Re: [Openstack] Why Image upload functionality is not there in orizon ?
Brian, Everyone Else, I added that in Folsom. You can create images if the actual image file is hosted elsewhere (not a local upload through the UI.) Here is a screenshot for the functionality: http://i.imgur.com/mYYV0.png John Postlethwait Nebula, Inc. 206-999-4492 On Friday, August 10, 2012 at 7:34 AM, Brian Waldon wrote: > Even being able to add images while providing an external location would be > useful. You could depend on your user to put it in swift or s3 and just > provide a uri that references it. > > On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote: > > > Indeed, uploading large files with the Horizon webserver as an intermediate > > relay is a nasty business which we want to discourage. We are looking at > > ways to send files directly from the Horizon client-side UI to swift/glance > > for large file upload in the future. > > > > All the best, > > > > - Gabriel > > > > > -Original Message- > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net) > > > [mailto:openstack- > > > bounces+gabriel.hurley=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net)] On Behalf Of Jay > > > Pipes > > > Sent: Thursday, August 09, 2012 10:43 AM > > > To: openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > > > Subject: Re: [Openstack] Why Image upload functionality is not there in > > > Horizon ? > > > > > > On 08/09/2012 02:35 AM, Sajith Kariyawasam wrote: > > > > Hi all, > > > > > > > > After playing around with Openstack Mangement Console, Horizon, I > > > > realize that the image upload functionality is not provided there. > > > > > > > > Is there any special reason for that? Is it because there are no Rest > > > > services available at the moment? or else is it felt that providing > > > > image upload via the UI is not practically important? > > > > > > > > > > > > > Probably because sending 20G Windows image files through a web form > > > interface isn't very efficient ;) > > > > > > It's also not something a "regular user" of Glance/Nova would do -- and > > > system administrators won't do it very often, and when they do, they'll > > > use > > > the glance CLI tool to do it. > > > > > > Best, > > > -jay > > > > > > ___ > > > Mailing list: https://launchpad.net/~openstack > > > Post to : openstack@lists.launchpad.net > > > (mailto:openstack@lists.launchpad.net) > > > Unsubscribe : https://launchpad.net/~openstack > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Why Image upload functionality is not there in Horizon ?
Sajith, I added that functionality in Folsom, you will not see it in Essex... John Postlethwait Nebula, Inc. 206-999-4492 On Sunday, August 12, 2012 at 11:12 PM, Sajith Kariyawasam wrote: > > > On Fri, Aug 10, 2012 at 11:15 PM, Gabriel Hurley (mailto:gabriel.hur...@nebula.com)> wrote: > > Horizon already has what you just described. You can load images into > > glance by providing a URI. It's the "Create Image" button on the Images > > table. > > What is the version you are referring to ? I have installed Openstack "Essex" > version, but in Openstack Dashboard, Images and Snapshots section I cannot > find a "Create Image" button as you have mentioned. :( > > > > > - Gabriel > > > > > -Original Message- > > > From: Brian Waldon [mailto:bcwal...@gmail.com] > > > Sent: Friday, August 10, 2012 7:35 AM > > > To: Gabriel Hurley > > > Cc: openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > > > Subject: Re: [Openstack] Why Image upload functionality is not there in > > > Horizon ? > > > > > > Even being able to add images while providing an external location would > > > be > > > useful. You could depend on your user to put it in swift or s3 and just > > > provide > > > a uri that references it. > > > > > > On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote: > > > > > > > Indeed, uploading large files with the Horizon webserver as an > > > intermediate relay is a nasty business which we want to discourage. We are > > > looking at ways to send files directly from the Horizon client-side UI to > > > swift/glance for large file upload in the future. > > > > > > > > All the best, > > > > > > > >- Gabriel > > > > > > > >> -Original Message- > > > >> From: openstack- > > > bounces+gabriel.hurley=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net) > > > >> [mailto:openstack- > > > >> bounces+gabriel.hurley=nebula@lists.launchpad.net > > > >> (mailto:nebula@lists.launchpad.net)] On Behalf Of > > > >> bounces+Jay > > > >> Pipes > > > >> Sent: Thursday, August 09, 2012 10:43 AM > > > >> To: openstack@lists.launchpad.net > > > >> (mailto:openstack@lists.launchpad.net) > > > >> Subject: Re: [Openstack] Why Image upload functionality is not there > > > >> in Horizon ? > > > >> > > > >> On 08/09/2012 02:35 AM, Sajith Kariyawasam wrote: > > > >>> Hi all, > > > >>> > > > >>> After playing around with Openstack Mangement Console, Horizon, I > > > >>> realize that the image upload functionality is not provided there. > > > >>> > > > >>> Is there any special reason for that? Is it because there are no > > > >>> Rest services available at the moment? or else is it felt that > > > >>> providing image upload via the UI is not practically important? > > > >> > > > >> Probably because sending 20G Windows image files through a web form > > > >> interface isn't very efficient ;) > > > >> > > > >> It's also not something a "regular user" of Glance/Nova would do -- > > > >> and system administrators won't do it very often, and when they do, > > > >> they'll use the glance CLI tool to do it. > > > >> > > > >> Best, > > > >> -jay > > > >> > > > >> ___ > > > >> Mailing list: https://launchpad.net/~openstack > > > >> Post to : openstack@lists.launchpad.net > > > >> (mailto:openstack@lists.launchpad.net) > > > >> Unsubscribe : https://launchpad.net/~openstack > > > >> More help : https://help.launchpad.net/ListHelp > > > > > > > > > > > > > > > > ___ > > > > Mailing list: https://launchpad.net/~openstack > > > > Post to : openstack@lists.launchpad.net > > > > (mailto:openstack@lists.launchpad.net) > > > > Unsubscribe : https://launchpad.net/~openstack > > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > > -- > Best Regards > Sajith > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Angry People and OpenStack
This should have the kibosh put on it, like, right now. I really do not see what good could come of this discussion on the mailing list. I, personally, know nothing about the details of this supposed email, her running, or her withdrawal, but I see no point in theory-crafting on the mailing list about a supposed scandal... This entire article reads as something specifically written to cause people to take sides and talking about it on the mailing list can serve no purpose that I see other than causing fragmentation, rumor-mongering, and anger. Maybe I am wrong, but this should die here... John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, August 1, 2012 at 1:13 PM, Frans Thamura wrote: > just got twit > > People Are Getting REALLY Angry Over OpenStack, A Key Cloud Tech by > @Julie188 read.bi/OpLhJM (http://read.bi/OpLhJM) > > > anyone wanna confirmation? > > > F > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [nova] Proposal to add Padraig Brady to nova-core
+1 for more core contributors! John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, July 18, 2012 at 4:09 PM, Vishvananda Ishaya wrote: > Hello Everyone! > > Padraig has been contributing a lot of code to all parts of nova, and has > been contributing a lot to reviews[1]. I think he would make a great addition > to nova-core. > > > [1] https://review.openstack.org/#/dashboard/1812 > > > Vish > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] About images list in dashboard
That's good to hear Sam! John Postlethwait Nebula, Inc. On Tuesday, July 17, 2012 at 4:24 PM, Sam Su wrote: > > I tried this backport in my mini environment, it looks like works fine. Thank > you, Gabriel. > > Thanks, > Sam > > On Sun, Jul 15, 2012 at 12:19 AM, Gabriel Hurley (mailto:gabriel.hur...@nebula.com)> wrote: > > > > Already happened. > > https://github.com/openstack/horizon/commit/fec36c45dbbca4f3b446cdb231f53e4ab2f6f507 > > > > > > > > > > > > Since they didn’t specify when/how they installed Essex, I’m going to > > assume they got a version that did not include this backport. > > > > > > > > > > > > All the best, > > > > > > > > > > > > - Gabriel > > > > > > > > > > > > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > (mailto:nebula@lists.launchpad.net) > > [mailto:openstack-bounces+gabriel.hurley > > (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net > > (mailto:nebula@lists.launchpad.net)] On Behalf Of Matt Joyce > > Sent: Friday, July 13, 2012 5:13 PM > > To: Christian Parpart > > Cc: mailto:openstack@lists.launchpad.net)> > > > > > > Subject: Re: [Openstack] About images list in dashboard > > > > > > > > > > > > > > > > I agree if someone wants to commit a backported fix. This makes sense to > > do. It's a pretty significant bug for essex users. > > > > -Matt > > > > > > On Fri, Jul 13, 2012 at 3:00 PM, Christian Parpart > (mailto:tra...@gmail.com)> wrote: > > > > > > On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait > > mailto:john.postlethw...@nebula.com)> wrote: > > > > > > > > > > Well, it sounds like this issue only happens in Essex, and is no longer > > > an issue in Folsom, so the bug will just be closed as invalid, as it is > > > now fixed in the newer code... > > > > > > > > > > > > > > > > > > > > > > Please backport this bug then. That is, the bug report indeed makes > > absolutely sense to me. :-) > > > > > > > > > > > > > > > > > > > > > > > > > > John Postlethwait > > > > > > > > > > > > Nebula, Inc. > > > > > > > > > > > > 206-999-4492 (tel:206-999-4492) > > > > > > > > > > > > > > > > > > > > > > > > > > > On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: > > > > > > > > Thank you for you guys' suggestions. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Even so, I'd like to file a bug to track this issue, if someone else > > > > have the same problem, they would know what happened and what > > > > progressed from the bug trace. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sam > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley > > > > mailto:gabriel.hur...@nebula.com)> wrote: > > > > > > > > > > > > > > > > > > > > Glance pagination was added in Folsom. Adding a bug for this won’t help > > > > since it’s already been added in the current code. > > > > > > > > > > > > > > > > > > > > > > > > - Gabriel > > > > > > > > > > > > > > > > > > > > > > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > > > (mailto:nebula@lists.launchpad.net) > > > > [mailto:openstack-bounces+gabriel.hurley > > > > (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net > > > &
Re: [Openstack] Identity API v3 - Why allow multi-tenant users?
Forcing a user to remember different usernames and/or passwords for each project they are a part of, when it is possible they are part of N projects, really isn't an acceptable option in my opinion. I believe that regardless of the engineering complexities, the end users shouldn't have to feel pain in order to make engineering the solutions and features they interact with easier. Software is for end users (in their various forms) and as such we need to take that into account when we make decisions. While no functionality is lost per se, there is a major end-user impact, and that should be reason enough to implement it… John Postlethwait Nebula, Inc. 206-999-4492 On Tuesday, July 17, 2012 at 4:15 PM, Rouault, Jason (Cloud Services) wrote: > > One benefit is the user does not need to have multiple sets of credentials to > interact with multiple projects. > > > > > > Jason > > > > > > From: openstack-bounces+jason.rouault=hp@lists.launchpad.net > [mailto:openstack-bounces+jason.rouault=hp@lists.launchpad.net > (mailto:hp@lists.launchpad.net)] On Behalf Of Adam Young > Sent: Tuesday, July 17, 2012 11:55 AM > To: openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Subject: Re: [Openstack] Identity API v3 - Why allow multi-tenant users? > > > > > > > > On 05/29/2012 01:18 PM, Caitlin Bestler wrote: > > > > > > One of the major complication I see in the API is that users can be > > associated with multiple tenants. > > > > > > > > > > > > What is the benefit of this? What functionality would be lost if a human > > user merely had to use a different account with each tenant? > > > > > > > > > > > > There are numerous issues with multi-tenant users. For example, if a user > > is associated with multiple tenants, who resets the user’s password? > > > > > > > > > > > > > > > > > > > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > Did you ever get an answer? This has been discussed in depth. > > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] About images list in dashboard
Well, it sounds like this issue only happens in Essex, and is no longer an issue in Folsom, so the bug will just be closed as invalid, as it is now fixed in the newer code... John Postlethwait Nebula, Inc. 206-999-4492 On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: > Thank you for you guys' suggestions. > > Even so, I'd like to file a bug to track this issue, if someone else have the > same problem, they would know what happened and what progressed from the bug > trace. > > Sam > > On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley (mailto:gabriel.hur...@nebula.com)> wrote: > > > > Glance pagination was added in Folsom. Adding a bug for this won’t help > > since it’s already been added in the current code. > > > > > > > > > > > > - Gabriel > > > > > > > > > > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > (mailto:nebula@lists.launchpad.net) > > [mailto:openstack-bounces+gabriel.hurley > > (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net > > (mailto:nebula@lists.launchpad.net)] On Behalf Of John Postlethwait > > Sent: Friday, July 13, 2012 12:05 PM > > To: Sam Su > > Cc: openstack > > Subject: Re: [Openstack] About images list in dashboard > > > > > > > > > > > > > > > > Hi Sam, > > > > > > > > > > > > > > Would you mind filing a bug against Horizon with the details so that we can > > get it fixed? You can do so here: > > https://bugs.launchpad.net/horizon/+filebug > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > John Postlethwait > > > > > > > > Nebula, Inc. > > > > > > > > 206-999-4492 (tel:206-999-4492) > > > > > > > > > > > > > > > > On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: > > > > > > I finally found why this happened. > > > > > > > > > > > > > > > > > > If in one tenant, there are more than 30 images and snapshots so that > > > glance cannot return the images list in one response, some images and > > > snapshots will not be seen in the page Images & Snapshots of Horizon. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Sam > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 5, 2012 at 1:19 PM, Sam Su > > (mailto:susltd...@gmail.com)> wrote: > > > > > > > > > > > > > > > Thank you for your suggestion. > > > > > > > > > > > > > > > > > > > > > > > > I can see all images in other tenants from dashboard, so I think the > > > images type should be ok. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley > > > mailto:gabriel.hur...@nebula.com)> wrote: > > > > > > > > > > > > > > > The “Project Dashboard” hides images with an AKI or AMI image type (as > > > they’re not launchable and generally shouldn’t be edited by “normal” > > > users). You can see those in the “Admin Dashboard” if you want to edit > > > them. > > > > > > > > > > > > > > > > > > So my guess is that the kernel and ramdisk images are being hidden > > > correctly and your “ubuntu-11.10-server-amd64” and > > > “ubuntu-12.04-server-amd64” have the wrong image type set. > > > > > > > > > > > > > > > > > > All the best, > > > > > > > > > > > > > > > > > > - Gabriel > > > > > > > > > > > > > > > > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net) &
Re: [Openstack] About images list in dashboard
Hi Sam, Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: > I finally found why this happened. > > If in one tenant, there are more than 30 images and snapshots so that glance > cannot return the images list in one response, some images and snapshots will > not be seen in the page Images & Snapshots of Horizon. > > > Sam > > > On Thu, Jul 5, 2012 at 1:19 PM, Sam Su (mailto:susltd...@gmail.com)> wrote: > > Thank you for your suggestion. > > > > I can see all images in other tenants from dashboard, so I think the > > images type should be ok. > > > > > > > > On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley > (mailto:gabriel.hur...@nebula.com)> wrote: > > > > > > The “Project Dashboard” hides images with an AKI or AMI image type (as > > > they’re not launchable and generally shouldn’t be edited by “normal” > > > users). You can see those in the “Admin Dashboard” if you want to edit > > > them. > > > > > > > > > > > > > > > > > > So my guess is that the kernel and ramdisk images are being hidden > > > correctly and your “ubuntu-11.10-server-amd64” and > > > “ubuntu-12.04-server-amd64” have the wrong image type set. > > > > > > > > > > > > > > > > > > All the best, > > > > > > > > > > > > > > > > > > - Gabriel > > > > > > > > > > > > > > > > > > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net) > > > [mailto:openstack-bounces+gabriel.hurley > > > (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net > > > (mailto:nebula@lists.launchpad.net)] On Behalf Of Sam Su > > > Sent: Thursday, July 05, 2012 11:20 AM > > > To: openstack > > > Subject: [Openstack] About images list in dashboard > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > I have an Openstack Essex environment. The nova control services, glance, > > > keystone and dashboard are all deployed in one server. > > > > > > > > > > > > Now I encounter a strange problem. I can only see two images (all images > > > are set is_public=true) in the tenant 'demo' from dashboard, i.e., > > > Horizon, as below: > > > > > > > > > > > > Image Name Type Status Public Container Format > > > Actions > > > > > > > > > > > > CentOS-6.2-x86_64 Image Active YesOVF > > > Launch > > > > > > > > > > > > CentOS-5.8-x86_64 Image Active YesOVF > > > Launch > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > However, when I use 'nova image-list' with the same credential for the > > > same tenant 'demo', I can see many more images (see the following result) > > > > > > > > > > > > > > > > > > > > > > > > # nova image-list > > > > > > > > > > > > +-+--+- > > > --+--+ > > > > > > > > > > > > | ID > > >| Name | > > > Status |Server | > > > > > > > > > > > > +-+--+--- > > > +--+ > > > &
Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom
So, in short, your entire purpose here is to troll everyone? Nice… : / You obviously care. You keep responding… You have been asked numerous times what we can do to NOT "stick us yet against in this situation in the future." Why is that such a difficult question to answer? Do you have an answer? Is your answer to "not change anything, ever"? That is not likely or reasonable – so what can be done here? Have you seen the other thread about what this cinder/nova-volume change entails? There ARE people here willing to hear it out if you have an answer, or an actionable suggestion, or process, or SOMETHING besides "get your heads out of your asses," which is hardly actionable, as it is vague and hopefully not a literal belief/suggestion… So, George: What do you want from us here? You likely have some legitimate pain-points, concerns, and reasons to be upset, but they are absolutely lost in your angry and personally offensive responses. Can you maybe elaborate on what pain THIS change would cause, and how we might assuage that? John Postlethwait Nebula, Inc. On Thursday, July 12, 2012 at 12:47 PM, George Reese wrote: > You are mistaking me for caring about the answer to this question. > > This ship has sailed. We are faced with two shitty choices as a result of > continued lack of concern by this community for compatibility. > > History? I've been pounding my head against the OpenStack all for years on > compatibility and we end up AGAIN in a situation like this where we have two > shitty options. > > I'm not offering an opinion or a third option because I just don't give a > damn what option is picked since both will suck. > > I'm trying to get everyone to get their heads out of their asses and not > stick us yet against in this situation in the future. > > You can discard my position if you want. I really don't give a damn. I just > happen to work with a wider variety of OpenStack environments that most > others on the list. > > But whatever. > > -George > > On Jul 12, 2012, at 2:40 PM, Jon Mittelhauser wrote: > > George, > > > > I am relatively new to this mailing list so I assume that there is some > > history that is prompting the vehemence but I do not understand what you > > are trying to accomplish. > > > > Vish sent out two proposed ways for dealing with the migration. Most of > > the early voting (including mine) has been for option #1 (happy to explain > > why if desired) but it isn't like the discussion is over. If you believe > > that option #2 is better, please explain why you believe that. If you > > believe that there is a 3rd option, please explain it to us. > > > > You are complaining without offering a counter proposal. That is simply > > not effective and makes semi-neutral folks (like me) tend to discard your > > point of view (which I assume is not your objective). > > > > -Jon > > > > From: George Reese > (mailto:george.re...@enstratus.com)> > > Date: Thursday, July 12, 2012 10:14 AM > > To: Brian Waldon > (mailto:brian.wal...@rackspace.com)> > > Cc: "Openstack (openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net)) (openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net))" > (mailto:openstack@lists.launchpad.net)> > > Subject: Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom > > > > Well, I think overall OpenStack has done an absolute shit job of > > compatibility and I had hoped (and made a huge point of this at the > > OpenStack conference) Diablo -> Essex would be the end of this > > compatibility bullshit. > > > > But the attitudes in this thread and with respect to the whole Cinder > > question in general suggest to me that this cavalier attitude towards > > forward migration hasn't changed. > > > > So you can kiss my ass. > > > > -George > > > > On Jul 12, 2012, at 12:11 PM, Brian Waldon wrote: > > > We actually care a hell of a lot about compatibility. We also recognize > > > there are times when we have to sacrifice compatibility so we can move > > > forward at a reasonable pace. > > > > > > If you think we are handling anything the wrong way, we would love to > > > hear your suggestions. If you just want to make comments like this, I > > > would suggest you keep them to yourself. > > > > > > Have a great day! > > > Brian Waldon > > > > > > On Jul 12, 2012, at 9:32 AM, George Reese wrote: &
Re: [Openstack] Compressed image support ?
Hi Wang, Horizon simply uses the Python interface to Glance and tells it to create the image. Glance supports creating images from remote locations that are in a compressed format. There are examples in the Glance documentation here: https://github.com/openstack/glance/blob/master/doc/source/glance.rst#examples-of-uploading-different-kinds-of-images and in the Glance binary itself here: https://github.com/openstack/glance/blob/master/bin/glance#L190 So this is widely supported and documented in Glance. The caveats are that through Horizon, the file MUST be accessible via the network configuration where Glance resides, if it is not accessible due to network configuration or something else, it will fail but seem to have succeeded. Also, you need to make sure you are linking DIRECTLY to the image itself, as if it is a redirect or any other HTTP response besides the file, Glance will still create an image out of it and it will seem to have worked. Sometimes you can even launch said instances that are totally invalid. (During my testing of this I was able to successfully launch instances that were just the HTTP data from 302 redirects.) I would first confirm that where Horizon is installed is able to communicate to where you are trying to copy the image from, and that the link you are using for the image is, in fact, a valid binary and not some other HTTP response. John Postlethwait Nebula, Inc. On Monday, July 9, 2012 at 1:04 AM, Wang Li wrote: > hi, all > > As to the horizon UI, zip and tar.gz image files are supported. > > """ > Specify an image to upload to the Image Service. > > Currently only images available via an HTTP URL are supported. The image > location must be accessible to the Image Service. Compressed image binaries > are supported (.zip and .tar.gz.) > > """ > > My test environment is as follow: > > 1. LVM as image backend of vms. > 2. running vms on Xen in PV mode > > But when I upload a tar gzipped raw image file, nova just dd from it to > logical volume, thus, nova error logged > > "Boot loader didn't return any data!" > > I grepped the nova and glance source code, found nothing about of "gz" or > "zip" that related to image. > > This feature is valuable to our use case, for the raw image file is 4GB, but > the compressed version is only 400MB. > > Did I misunderstand the compressed image support? > > > Regards. > Wang Li > > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] best practices for merging common into specific projects
I agree, I think moving them into one of the package/dependency managers the Open Stack projects already use is the proper way to do this. The current process of copying the "latest" seemingly un-versionable code around into the projects really bothered me when it just happened to Horizon for the JSON parser a few weeks ago, I wash;t too keen on approving that review and I'd like to get away from it if possible, even if done by a bot of some kind... John Postlethwait Nebula, Inc. 206-999-4492 On Monday, July 2, 2012 at 2:41 PM, Joshua Harlow wrote: > Re: [Openstack] best practices for merging common into specific projects What > about using openstack-common as a library instead of a preprocessor > ‘inclusion’ system/copy code around system?? > > Maybe its time for that to happen? > > It always seemed sort of silly to me that files are being copied around to > different projects like this, instead of referring to code in a common > library package. > > On 7/2/12 12:16 PM, "Andrew Bogott" wrote: > > > Having spent some time last week writing code for openstack-common, > > and having spent yet more time trying to get those changes into Nova, I > > think it would be useful to define some best practices when crossing the > > boundary between common and other openstack projects. > > > > Background: > > > > The openstack-common project is subject to a standard code-review > > process (and, soon, will also have Jenkins testing gates.) Sadly, > > patches that are merged into openstack-common are essentially orphans. > > Bringing those changes into actual use requires yet another step, a > > 'merge from common' patch where the code changes in common are copied > > into a specific project (e.g. nova.) > > Merge-from-common patches are generated via an automated process. > > Specific projects express dependencies on specific common components via > > a config file, e.g. 'nova/openstack-common.conf'. The actual file copy > > is performed by 'openstack-common/update.py,' and its behavior is > > governed by the appropriate openstack-common.conf file. > > > > Questions: > > > > When should changes from common be merged into other projects? > > What should a 'merge-from-common' patch look like? > > What code-review standards should core committers observe when > > reviewing merge-from-common patches? > > > > Proposals: > > > > I. As soon as a patch drops into common, the patch author should > > submit merge-from-common patches to all affected projects. > > A. (This should really be done by a bot, but that's not going to > > happen overnight) > > > > II. In the event that I. is not observed, merge-from-common patches > > will contain bits from multiple precursor patches. That is not only OK, > > but encouraged. > > A. Keeping projects in sync with common is important! > > B. Asking producers of merge-from-common patches to understand the > > full diff will discourage the generation of such merges. > > > > III.Merge-from-common patches should be the product of a single > > unedited run of update.py. > > A. If a merge-from-common patch breaks pep8 or a test in nova, > > don't fix the patch; fix the code in common. > > > > IV.Merge-from-common patches are 'presumed justified'. That means: > > A. Reviewers of merge-from-common patches should consider test > > failures and pep8 breakages, and obvious functional problems. > > B. Reviewers of merge-from-common patches should not consider the > > usefulness, design, etc. of merge-from-common patches. Such concerns > > need to be handled within the common review process. > > C. Merges from common should get reviewed early and approved > > readily in order to avoid project divergence > > > > V. Changes to openstack-common.conf are a special case. > > A. Patches with openstack-common.conf changes should include the > > relevant merge-from-common changes. > > B. Such patches should /not/ include any other merge-from-common > > changes. > > C. Such patches should not only include the common merges, but > > should also include whatever code changes make use of the new merge. > > D. Such patches require the same justification and scrutiny as any > > other standard project patch. > > > > Please discuss! If we're able to reach general agreement about this > > process, I will document the process in the
Re: [Openstack] Jenkins
Yes, it is currently being worked on... John Postlethwait Nebula, Inc. On Wednesday, June 27, 2012 at 10:04 AM, Gary Kotton wrote: > Hi, > Is anyone aware of a problem with Jenkins? > Thanks > Gary > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Swift] Problem with merging
Jenkins has been broken since yesterday. The infrastructure team is trying to address that now, it will merge when it is back up. John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, June 27, 2012 at 9:09 AM, Victor Rodionov wrote: > Hello > > I have patch https://review.openstack.org/#/c/7565/ (Patch for Swift > Solaris (illumos) compatibility), that was approved, but during merging > something goes wrong. It seems it's jenkins preblem, can someone whe > responsible for this, start merging again please. > > > Thanks, > Victor > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova doesn't release ips when terminating instances
Seems like this might be a pretty valid issue to report/fix though, no? I would assume those IPs should be unallocated/released if they are no longer attached to anything... John Postlethwait Nebula, Inc. 206-999-4492 On Saturday, June 23, 2012 at 11:06 AM, Belmiro Moreira wrote: > Hi, > can you try with the flag: > force_dhcp_release=false > > But first you need to: > > Manually set instance_id=NULL in the fixed_ips table allows things to > > work again. > > > > > > Belmiro > CERN > > > On Jun 23, 2012, at 5:11 AM, Lars Kellogg-Stedman wrote: > > > When an instance terminates, the "allocated" field in the fixed_ips is > > set to "0", but the "instance_id" field remains set. Once all the > > addresses are in this state, new instances fail to start, and the > > following error is logged by nova-network: > > > > 2012-06-22 23:09:34 ERROR nova.rpc.amqp > > [req-1fea207d-cd65-4375-9a04-17ba1ab92e3e > > 22bb8e502d3944ad953e72fc77879c2f 76e2726cacca4be0bde6d8840f88c136] > > Returning exception Zero fixed ips available. to caller > > > > Which shows up in compute.log as: > > > > 2012-06-22 23:08:35 TRACE nova.rpc.amqp RemoteError: Remote error: > > NoMoreFixedIps Zero fixed ips available. > > > > Manually set instance_id=NULL in the fixed_ips table allows things to > > work again. > > > > We're running the 2012.1.1 release and we're using the FlatDHCP model. > > Is this a known bug? > > > > Thanks, > > > > -- > > Lars Kellogg-Stedman mailto:l...@seas.harvard.edu)> > > | > > Senior Technologist | http://ac.seas.harvard.edu/ > > Academic Computing | http://code.seas.harvard.edu/ > > Harvard School of Engineering and Applied Sciences | > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Tihomir Trifonov added to horizon-core
Welcome indeed! You have been doing great work and we all appreciate it! John Postlethwait Nebula, Inc. 206-999-4492 On Friday, June 22, 2012 at 1:45 PM, Devin Carlen wrote: > Welcome Tihomir to horizon-core! Thanks for all the great contributions in > the past months! > > > Devin > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Metering] Implemented three methods in Ceilometer
That simply appears that you have a network issue… Perhaps a firewall at work blocking that port number, or a DNS issue, or a temporary issue with review.stackforge.org? John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, June 21, 2012 at 11:37 PM, Kobagana Kumar wrote: > Hi Julien Danjou, > > I followed the steps given in http://wiki.openstack.org/GerritWorkflow this > site. But I am getting some error while executing the command "git review". > > While I am executing that command I am getting following error: > > Problem running 'git remote update gerrit' > Fetching gerrit > ssh: connect to host review.stackforge.org (http://review.stackforge.org) > port 29418: Connection timed out > fatal: The remote end hung up unexpectedly > error: Could not fetch gerrit > > Can you please tell me the way to resolve this error. > > Thanks & Regards, > > Bharath Kumar > > -Original Message- > From: Julien Danjou [mailto:julien.dan...@enovance.com] > Sent: Wednesday, June 20, 2012 2:13 PM > To: Kobagana Kumar > Cc: openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Subject: Re: [Openstack] [Metering] Implemented three methods in Ceilometer > > On Wed, Jun 20 2012, Kobagana Kumar wrote: > > Hi Kobagana, > > > I have implemented three more classes in Ceilometer plug-in module. > > Added those classes in libvirt.py file in compute. > > The classes which I have added are counters to find out the following: > > > > 1. Number of CPUs used > > > > 2. Memory used > > > > 3. Maximum memory used > > I am also ready with test cases for those methods. > > > > Please let me know the procedure to contribute my code to ceilometer > > code base. > > > > > You need to send your patches to https://review.stackforge.org/ using > git-review. > > You can find some documentation about this here: > > http://wiki.openstack.org/GerritWorkflow > > -- > Julien Danjou > // eNovance http://enovance.com > // ✉ julien.dan...@enovance.com (mailto:julien.dan...@enovance.com) ☎ +33 1 > 49 70 99 81 > > DISCLAIMER > == > This e-mail may contain privileged and confidential information which is the > property of Persistent Systems Ltd. It is intended only for the use of the > individual or entity to which it is addressed. If you are not the intended > recipient, you are not authorized to read, retain, copy, print, distribute or > use this message. If you have received this communication in error, please > notify the sender and delete all copies of this message. Persistent Systems > Ltd. does not accept any liability for virus infected mails. > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Comparing roles - case (in)sensitivity
I'm going to be the counter opinion here, but I don't really see a benefit in the case-sensitivity from a user perspective… Will a user ever want a scenario where they have/can have an "Admin" and an "admin" role (and maybe even an "adMIN" role)? I could certainly be missing a lot of context here, but I tend to think of role names a human identifiers, and case sensitive human groups doesn't seem to serve much human purpose here where "Admin" and "admin" are not the same role... John Postlethwait Nebula, Inc. 206-999-4492 On Friday, June 8, 2012 at 3:08 PM, Zach Borboa wrote: > Explicit is better than implicit. Case-sensitive. > > On Fri, Jun 8, 2012 at 2:50 PM, Brian Waldon (mailto:brian.wal...@rackspace.com)> wrote: > > tl;dr - Should we compare roles as case-sensitive or case-insensitive? I > > vote case-sensitive. > > > > This bug was recently filed in > > Glance: https://bugs.launchpad.net/glance/+bug/1010519. It points out that > > Nova and Keystone are both case-insensitive when it comes to role > > comparison, yet Glance *is* case sensitive. I'm in favor of moving other > > projects to a case-sensitive approach for two main reasons: > > > > 1) If a role is a string, and comparing strings is inherently > > case-sensitive, then role comparison would logically be case-sensitive > > 2) I get to do less work > > > > Thoughts? > > > > Brian Waldon > > > > > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] new version of gerrit - with new features!
Really awesome stuff, thank you guys! John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, June 7, 2012 at 3:46 PM, Monty Taylor wrote: > Hey guys! > > We just upgraded to a new version of gerrit. This is based on the new > upstream version 2.4, but in addition we've landed two additional > features on top of that - so there's tons of new toys to play with. > > First of all, in 2.4 upstream has added a new button "Rebase Change" ... > which you can use to rebase your change on top of the current tip of the > target branch from within gerrit itself. Also, upstream has been working > on adding a proper REST interface, instead of json-rpc which is what > they have been using. I'm not sure how far that's gotten, but I believe > it can do a decent amount of stuff for those of you who like, you know, > REST-based scripting. > > In addition to that, we've got two main features we've landed as well. > > David Shrewsbury wrote a long-requested feature: a Work In Progress > state. Changes will now have a Work In Progress button on them that can > be used to mark the change as something that the dev is working on > again, so that other folks know they don't need to review it. The button > is available to the author of the patch, as well any group that we > assign to have access. In our case, we'll be granting $project-core Work > In Progress permission. Putting something back into the "ready for > review" state can be done one of two ways - either by just uploading a > new patch to the change, or by clicking the "Ready for Review" button. > > Hand in hand with that change, Clark Boylan has written an "Important > Changes" view - which shows all on one page the changes that a developer > should be looking at. On the page are changes that were uploaded by the > developer (same as the "My Changes" page), then a section for changes > that the developer should be reviewing, which are changes that the dev > has either watched, starred, or that reviews have been requested, and > that are no in work in progress state and additionally that the dev has > not already reviewed. Finally, there is a section for changes that the > developer has already reviewed, in case they need to be further tracked. > > We're hoping that some of these things help to reduce a little bit of > the burden in terms of tracking which things should be watched. We'll be > working on getting our patches upstreamed in the near future... but > since they are new workflow possibilities, we're happy to get feedback > on ways in which they could be more useful to folks. > > Also - we have an open question - which is, if the pre-approval check > jobs fail in Jenkins, should the patch be automatically marked Work In > Progress. We're not going to do that right out of the gate, but would > love feedback on what people think. > > Thanks everybody! > Monty > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Integration Test Failing for Review
Thanks a lot for looking in to it! John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, June 7, 2012 at 5:31 AM, Andrew Hutchings wrote: > On 07/06/12 09:13, Thierry Carrez wrote: > > John Postlethwait wrote: > > > I have a review up that keeps failing the integration tests on Jenkins > > > due to some sort of dependency issue. I am not really sure what the > > > issue is, but the stack trace in the console output is complaining about > > > "No module named version tools.setuptools_hooks" from within Django > > > Appconfig, see > > > here: > > > https://jenkins.openstack.org/job/gate-integration-tests-devstack-vm/4629/console > > > > > > Is there something I need to do/can be done to make this run? Here is > > > the review: https://review.openstack.org/#/c/7367/ > > > > > > > > > For mysterious gate fails, my technique involves asking the CI team to > > look into the particular failure and explain it to me :) You can find > > them on #openstack-infra. > > > > > I can see why this is happening, just not quite sure on the best course > of action to fix it. I've asked others on our team more familiar with > pip to help. > > Kind Regards > -- > Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Proposal to add Tihomir Trifinov to Horizon Core
I absolutely agree with this sentiment. Tihomir has been doing an amazing job and has been extremely attentive and helpful. John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, June 6, 2012 at 12:12 PM, Gabriel Hurley wrote: > A couple of us on the Horizon team have been talking, and we'd like to > recognize the tremendous work the Tihomir has been doing on Horizon for the > past 6+ months by making him a member of Horizon Core. He's been writing > great code, doing consistent and helpful reviews, tackling important bugs, > and all around being an excellent contributor. I certainly trust his judgment > at this point. > > I believe the "official" process is to propose new additions to the core > teams on the mailing list, so... that's what I'm doing. > > All the best, > > - Gabriel > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Integration Test Failing for Review
Hello Everyone! I have a review up that keeps failing the integration tests on Jenkins due to some sort of dependency issue. I am not really sure what the issue is, but the stack trace in the console output is complaining about "No module named version tools.setuptools_hooks" from within Django Appconfig, see here: https://jenkins.openstack.org/job/gate-integration-tests-devstack-vm/4629/console Is there something I need to do/can be done to make this run? Here is the review: https://review.openstack.org/#/c/7367/ John Postlethwait Nebula, Inc. 206-999-4492 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Fwd: Nodejs in horizon
Hi Everyone, Sorry if I've missed anything below, this thread has become rather fragmented and messy (at least in my email clients) but I will try to address the main points I have seen so far: * Just so that everyone is aware, the lessc parser that is bundled in Horizon, while executable, is NOT a binary. It is, in fact, just a 140 line JS file, you can see the code here: https://review.openstack.org/#/c/7367/4/bin/less/lessc * The reason I have bundled it within the Horizon code, as Gabriel mentioned, is to assuage any version mismatches or install issues with LESS itself that may arise from having yet another dependency on top of NodeJS that needs manual steps to install. Also, the LESS package that exists for Ubuntu is a year out of date, and other distributions do not even have packages for it. I would love if we could rely on the OS' packages to assuage this dependency, but we cannot, so this is the simplest and best-working solution I could think of. It will be no more difficult to maintain than jQuery, or Bootstrap, in the Horizon code-base... * As for distribution support, Node can be installed on just about anything, see here: https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager * As to the concerns about "it not being Python" or "JavaScript has been abused." Well, all I can say to that is no, it is not Python, and yes, some developers write terrible and abusive code with JavaScript. I'm sure I could find horrid/abusive Python somewhere as well, but doing so would not preclude our reasons to use it in OpenStack. Misuse of a tool is not a reason to fear the tool itself, if that were so none of us would use any language, ever. Not to mention, we already use a ton of JS in Horizon... I'm not introducing JavaScript to Horizon for the first time or anything here. I'm sure I've missed some good points, but this thread is a mess and is difficult to sort through... :P -John Postlethwait From: openstack-bounces+john.postlethwait=nebula@lists.launchpad.net [openstack-bounces+john.postlethwait=nebula@lists.launchpad.net] on behalf of Simon G. [semy...@gmail.com] Sent: Friday, May 25, 2012 7:40 AM To: Jay Pipes Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Fwd: Nodejs in horizon Maybe I've misuderstood something, but I've tried to give examples of other backends than node.js which can make use of mentioned before socket.io<http://socket.io> and can be used to implement realtime communication. I just wanted to minimize use of node.js. Hmm... I'm still talking about realtime communication, but it was only mentioned as an example and it's not even listed as a feature anywhere. So maybe my part in this topic is pointless. I'll be silent from now :) Cheers, On Fri, May 25, 2012 at 3:20 PM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: On 05/25/2012 08:41 AM, Simon G. wrote: Hello, I don't want to be rude, but fast research about point *3c* and sockets => PyPi search <http://pypi.python.org/pypi?%3Aaction=search&term=socket.io&submit=search> * http://pypi.python.org/pypi/SocketTornad.IO/ * http://pypi.python.org/pypi/TornadIO2/0.0.3 , https://github.com/MrJoes/tornadio2 * http://pypi.python.org/pypi/django-socketio/0.3.3 * http://mrjoes.github.com/2011/12/15/sockjs-bench.html How mature are those projects? I don't know. I'm not an expert in python. I'm just trying to find alternatives to Node.js if almost everything is in python. I'm just testing Openstack and right now I'm trying to add something to nova, but I really like horizon and if it's possible, I'd like to avoid node.js. I'm not a fan of this technology even if it's popular and fast, because I just have some doubts about Javascript and its maintainability. Hi Simon, socket.io<http://socket.io> is a Javascript library :) 3 of the 4 projects you reference above use socket.io<http://socket.io>. Best, -jay ___ Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack> Post to : openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net> Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack> More help : https://help.launchpad.net/ListHelp -- Semy ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Glance] Using HTTP PATCH
Patch certainly seems more semantically proper in this context, and I love being semantically proper using HTTP… That being said I am not currently sure of any places where this might be a problem. There was mention of the firewall issues, but I don't know if that is necessarily true. Do firewalls typically/ever do deep inspections of HTTP headers in the communication and filter on the HTTP method? It wouldn't even be able to do such a thing if you are using HTTPS, would it? John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, May 23, 2012 at 2:02 PM, Brian Waldon wrote: > Relevant links: > > https://review.openstack.org/#/c/7716/ > http://tools.ietf.org/html/rfc5789 > http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/ > > > On May 23, 2012, at 1:22 PM, Brian Waldon wrote: > > Hey guys, > > > > I'm considering using PATCH rather than PUT for image updates in the v2 > > Image API, but I wanted to make sure there weren't any major blockers that > > I might be missing. As far as I can tell, the python libraries we use in > > Glance support it (httplib2, requests). However, I discovered that Squid > > doesn't document official support of the method: > > http://wiki.squid-cache.org/SquidFaq/SquidLogs. I wanted to ask if there > > are any other key infrastructure pieces that foolishly hard-code request > > methods like this. It might make us want to rethink using PATCH at all. > > > > Brian___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto:openstack@lists.launchpad.net) > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Running review requests code on jenkins.openstack.org
Hello Victor, Please see here: http://wiki.openstack.org/GerritJenkinsGithub#line874 (Under the "Reviewing a Change" header.) John Postlethwait Nebula, Inc. 206-999-4492 On Monday, April 30, 2012 at 1:49 PM, Victor Rodionov wrote: > Hello > > How I can run my code on Openstack jenkins server, for verifie it? > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Code contribution
If you are asking how it becomes approved the answer is that two core-contributors of the specific project need to manually review the code, and +2 it. When that is done, Jenkins, a CI tool, will run the various automated acceptability tests against the code and if they all pass, it will merge it in to the project. John Postlethwait Nebula, Inc. 206-999-4492 On Friday, April 27, 2012 at 9:08 AM, Victor Rodionov wrote: > Hello > > How code in gerrit becomes verified? > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Using Nova APIs from Javascript: possible?
TL;DR for the below: +1 to what Nick said. I think both sides here are valid... Yes, security issues are opened up with these technologies, and they are indeed rather new, but the use-case for wanting to access the files in this manner also definitely exists. Whatever solution is decided on, we should do it in a manner that allows someone installing OpenStack to entirely shut to off/not use it, OR to open it up to JSONP/CORS/whatever and have Tres' use-cases supported. The risk is up to the installer depending on their needs/use-cases. We should support them AND do a good job of educating them of the risks and rewards of using such technologies. It shouldn't be up to us to determine if it is theoretically a good idea or not, or if it is necessary, or if it could be done in a different way, or if their desire is off-base, but we should support the functionality in an intelligent manner and let the installer decide on what/how/why they want to use and install OpenStack… John Postlethwait Nebula, Inc. 206-999-4492 On Wednesday, April 25, 2012 at 10:01 AM, Jan Drake wrote: > A little of both. Serving JS, et al from a CDN for a set of domain services > is easy peasey stuff and we do it all the time... but we tend to do so with a > common edge (at the very least in DNS space) that precludes the need for > JSONP/CORS. I'm not sure if the use case here is: > > 1) JS client talking to multiple service providers hosting openstack, (seems > low priority to me but potentially valid) > 2) JS client talking to multiple openstack services within a single hosting > provider (seems high priority to me) > > #2 is easy we do it all the time. #1 gets messy but I probably wouldn't just > use a JS only mashup client to get the job done. > > Anyway, just thoughts... re maturity: our enterprise security folks have > issues with using jsonp/cors and consider it contraindicated at the moment. > > > > Jan > > > Subject: Re: [Openstack] Using Nova APIs from Javascript: possible? > From: t...@treshenry.net (mailto:t...@treshenry.net) > Date: Wed, 25 Apr 2012 09:49:15 -0700 > CC: openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > To: jan_dr...@hotmail.com (mailto:jan_dr...@hotmail.com) > > Jan: is the concern that you don't see the value in the use case or that you > don't believe the proposed technologies are sufficiently mature? > > In order to keep the thread somewhat linear I'm basically going to +1 what > Nick said and add that as an application developer I should be able to serve > the JS, HTML and CSS for my application from a CDN and have my application > talk directly to an OpenStack endpoint. This is an important scenario now but > will become critical with the wave of PAAS offerings coming for OpenStack > (i.e. my application should be able to talk directly to FathomDB running on > OS). > > > On Apr 25, 2012, at 3:46 AM, Nick Lothian wrote: > > JSONP has been used for years - for example Solr has supported it since > > 2008 (and possibly earlier). CORS matches the Openstack APIs better though. > > > > Redirects are unrelated to the problem as far as I can see. > > I think that toolmakers trying to build Javascript tools that connect to > > multiple service providers is a completely valid use case. It is supported > > for pretty much any other language, why not Javascript? > > On Apr 25, 2012 12:33 PM, "Jan Drake" > (mailto:jan_dr...@hotmail.com)> wrote: > > > So, why such a focus on this? IMO both JSONP and CORS are way too early > > > stage to adopt and the security risks outweigh the rewards. Usually, I > > > see people doing this to enable mashups across separate providers. > > > > > > Just curious why the focus/need is perceived in the community? If this > > > is really because of redirects then we probably have a broken model > > > and/or improper distribution of responsibilities. > > > > > > Love to know if I'm missing a real use case. Can help fix model if it is > > > broken. Have much experience in this area. > > > > > > IMO no solution should trick the browser. > > > > > > > > > Jan > > > > > > > > > > > > On Apr 24, 2012, at 7:05 PM, Luis Gervaso > > (mailto:l...@woorea.es)> wrote: > > > > > > > The solution until the webservice deliver that headers is: > > > > > > > > Solution 1: > > > > > > > > 1. Put the webservice behind a remote or local proxy > > > > 2. Apply some a filter (decorator) for each response
Re: [Openstack] E4 - And So It Begins!
Thanks for this, this is great! I just started setting up everything last night and this helped me finalize all of that and get into the code myself! - John Postlethwait 206.999.4492 On Monday, January 30, 2012 at 8:32 PM, Brian Waldon wrote: > On Jan 30, 2012, at 8:58 AM, Jesse Andrews wrote: > > > Bug Squash Day > > > > > > We are doing a number of things in preparation for the Bug Squash day > > on Thursday. > > > > * Triaging bugs - hopefully all bugs will have a priority by Thursday > > * Tagging bugs with low-hanging-fruit if we feel that they are > > relatively easy fixes - This will give the folks that are new to the > > code base a place to get their feet wet: > > https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit > > * Preparing step-by-step documentation for installing a dev > > environment, getting set up with the CLA and gerrit, assigning > > yourself a bug and fixing it: > > http://wiki.openstack.org/BugSquashingDay > > * Creating OpenStack VMs for people to use at the SF Bug Squash Day > > Meetup: http://www.meetup.com/openstack/events/48362422/ > > I added a quickstart guide at http://wiki.openstack.org/DevQuickstart with an > introduction for new developers to OpenStack. It walks a newbie through > setting up a development environment, establishing accounts on all the > necessary systems, and fixing bugs. I aimed for the minimum amount of > information, so if anybody wants to add to it, keep that in mind. I went > ahead and added a link on the BugSquashingDay page as well. > > Brian Waldon > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net (mailto:openstack@lists.launchpad.net) > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
