That's all true. We've increased the timeout for now, however, the proper
fix requires quite some effort. We need to move the GridFS blobs to Swift
and then storage management will become simpler (production wise). This
also covers multi-charm store syncing at the same time. I'm also going to
propose that we introduce quotas for charm store on user namespace. You can
ask for more space but that's how we can prevent from some CI to upload
gigabytes of data per day by mistake. Log analysis will help as well, but
that's also on ToDo ATM :-/
On Sun, Jul 10, 2016 at 9:28 AM, John A Meinel <email address hidden>
wrote:
> Is this a case that we are successfully sending data to squid at a
> reasonable but slow rate, such that it takes more than 5 minutes to upload
> the whole content and squid doesn't send anything to Apache until all of it
> has been transferred.
> It sounds like we'll have the same problem with resources. While it might
> allow us to break up a large charm into a few smaller resources, AIUI some
> of the charms have a single tarball that is more than 1GB in size.
> Arbitrarily limiting the size is going to just cause people to work around
> the system (self hosting, etc) Which breaks many of the benefits of having
> resources (demure transfers, offline mirroring, etx)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1592822
>
> Title:
> Charm push crashes when pushing 'big' charm.
>
> Status in charm package in Ubuntu:
> Confirmed
>
> Bug description:
> running `charm push` for a very large charm causes a crash. Removing
> the largest files from the charm fixes the issue. If large charms are
> not supported, it might be better to throw a helpful error message.
>
>
> ```
> ERROR cannot post archive: cannot unmarshal error response "<!DOCTYPE
> html PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"
> http://www.w3.org/TR/html4/strict.dtd\">\n<html><head>\n<meta
> http-equiv=\"Content-Type\" content=\"text/html;
> charset=utf-8\">\n<title>ERROR: The requested URL could not be
> retrieved</title>\n<style type=\"text/css\"><!-- \n Internal Error: Missing
> Template MGR_INDEX\n\nbody\n:lang(fa) { direction: rtl; font-size: 100%;
> font-family: Tahoma, Roya, sans-serif; float: right; }\n:lang(he) {
> direction: rtl; }\n --></style>\n</head><body
> id=ERR_ZERO_SIZE_OBJECT>\n<div id=\"titles\">\n<h1>ERROR</h1>\n<h2>The
> requested URL could not be retrieved</h2>\n</div>\n<hr>\n\n<div
> id=\"content\">\n<p>The following error was encountered while trying to
> retrieve the URL: <a href=\"
> http://api.jujucharms.com/v5/~tengu-bot/trusty/rest2jfed/archive?\">
> http://api.jujucharms.com/v5/~tengu-bot/trusty/rest2jfed/archive?</a></p>\n\n<blockquote
> id=\"error\">\n<p><b>Zero Sized Reply</b></p>\n</blockquote>\n\n<p>Squid
> did not receive any data for this request.</p>\n\n<p>Your cache
> administrator is <a href=\"mailto:webmaster?subjec ... [3528 bytes
> omitted]": invalid character '<' looking for beginning of value
> ```
>
> Putting the charm in attachment causes a launchpad crash. Please let
> me know if I can upload the charm somewhere else.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1592822/+subscriptions
>
That's all true. We've increased the timeout for now, however, the proper
fix requires quite some effort. We need to move the GridFS blobs to Swift
and then storage management will become simpler (production wise). This
also covers multi-charm store syncing at the same time. I'm also going to
propose that we introduce quotas for charm store on user namespace. You can
ask for more space but that's how we can prevent from some CI to upload
gigabytes of data per day by mistake. Log analysis will help as well, but
that's also on ToDo ATM :-/
On Sun, Jul 10, 2016 at 9:28 AM, John A Meinel <email address hidden>
wrote:
> Is this a case that we are successfully sending data to squid at a /bugs.launchpad .net/bugs/ 1592822 www.w3. org/TR/ html4/strict. dtd\">\n<html> <head>\ n<meta \"Content- Type\" content= \"text/ html; utf-8\" >\n<title> ERROR: The requested URL could not be /title> \n<style type=\" text/css\ "><!-- \n Internal Error: Missing n\nbody\ n:lang( fa) { direction: rtl; font-size: 100%; \n</head> <body ZERO_SIZE_ OBJECT> \n<div id=\"titles\ ">\n<h1> ERROR</ h1>\n<h2> The /h2>\n< /div>\n< hr>\n\n< div ">\n<p> The following error was encountered while trying to api.jujucharms. com/v5/ ~tengu- bot/trusty/ rest2jfed/ archive?\"> api.jujucharms. com/v5/ ~tengu- bot/trusty/ rest2jfed/ archive?</a></p> \n\n<blockquote ">\n<p> <b>Zero Sized Reply</ b></p>\ n</blockquote> \n\n<p> Squid </p>\n\ n<p>Your cache webmaster? subjec ... [3528 bytes /bugs.launchpad .net/ubuntu/ +source/ charm/+ bug/1592822/ +subscriptions
> reasonable but slow rate, such that it takes more than 5 minutes to upload
> the whole content and squid doesn't send anything to Apache until all of it
> has been transferred.
> It sounds like we'll have the same problem with resources. While it might
> allow us to break up a large charm into a few smaller resources, AIUI some
> of the charms have a single tarball that is more than 1GB in size.
> Arbitrarily limiting the size is going to just cause people to work around
> the system (self hosting, etc) Which breaks many of the benefits of having
> resources (demure transfers, offline mirroring, etx)
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> Charm push crashes when pushing 'big' charm.
>
> Status in charm package in Ubuntu:
> Confirmed
>
> Bug description:
> running `charm push` for a very large charm causes a crash. Removing
> the largest files from the charm fixes the issue. If large charms are
> not supported, it might be better to throw a helpful error message.
>
>
> ```
> ERROR cannot post archive: cannot unmarshal error response "<!DOCTYPE
> html PUBLIC \"-//W3C//DTD HTML 4.01//EN\" \"
> http://
> http-equiv=
> charset=
> retrieved<
> Template MGR_INDEX\
> font-family: Tahoma, Roya, sans-serif; float: right; }\n:lang(he) {
> direction: rtl; }\n --></style>
> id=ERR_
> requested URL could not be retrieved<
> id=\"content\
> retrieve the URL: <a href=\"
> http://
> http://
> id=\"error\
> did not receive any data for this request.
> administrator is <a href=\"mailto:
> omitted]": invalid character '<' looking for beginning of value
> ```
>
> Putting the charm in attachment causes a launchpad crash. Please let
> me know if I can upload the charm somewhere else.
>
> To manage notifications about this bug go to:
> https:/
>