[Openstack] openstack dashboard default page changing

[sarath zacharia]

Hai ,

We created a new site for explaining our cloud research work.
But when we deployed that html page to openstack dashboard
folder then the page shows some permission problem like

   The page you were looking for doesn't exist

   You may have mistyped the address or the page may have
moved.

How can I change the default page of dashboard to home page of
our web page

please help me


-- 
with Thanks and Regards

Sarath Zacharia
___
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] Floating IPs and multiple NICs

[Ruzicka, Marek]

Hi Juris,

Yes it is possible. We are running 2 different public subnets on 2 different 
vlan interfaces.

Did you try something like:
nova-manage floating create --ip_range= --pool= 
--interface=

Hopefully I have it right, not at the computer atm... Let me know if it is 
working for you. If not, I'll crosscheck it.

Marek

Sent from my iPad

On 20.8.2012, at 18:47, "Juris"  wrote:

> Greetings everyone,
> 
> Just a quick question.
> Is it possible to assign floating IPs to multiple nova node interfaces?
> For instance if I have a server with 4 NICs and I'd like to use NIC1
> for private network, NIC2 for data and management, NIC3 for one of my
> public IP subnets and NIC4 for another public IP subnet?
> 
> Best wishes,
> Juris
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] Question about Flat DHCP networking

[hitesh wadekar]

Oh..I see.

I look forward to see your code for it :)

Thanks,
Hitesh

On Tue, Aug 21, 2012 at 11:27 AM, Eugene Kirpichov wrote:

> Heh, that's an article by my colleague Piotr Siwczak, which I already
> read very thouroughly during the review process - but thanks ;)
>
> Actually I already found the answer to my question and added it to the
> documentation (when the codereview is completed) - it was related to
> nova-dhcpbridge script.
>
> On Mon, Aug 20, 2012 at 10:21 PM, hitesh wadekar
>  wrote:
> > May be this article will help.
> >
> >
> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/
> >
> > Thanks,
> > Hitesh
> >
> >
> > On Tue, Aug 21, 2012 at 3:16 AM, Eugene Kirpichov 
> > wrote:
> >>
> >> Hi,
> >>
> >> I found the code. It's a dnsmasq dhcp-script called by dnsmasq for
> >> various events, it resides in nova/bin/nova-dhcpbridge and it, among
> >> other things, calls release_fixed_ip when the lease expires.
> >>
> >> On Sat, Aug 18, 2012 at 1:01 AM, Aaron Rosen  wrote:
> >> > Hi Eugene,
> >> >
> >> > I'm not sure I have not looked at the code (I'm guessing that it
> >> > probably
> >> > keeps the lease around since it knows the VM is still active instead
> of
> >> > recycling the ip address). Though this is just a guess. You should
> look
> >> > at
> >> > the implementation details if you are curious.
> >> >
> >> > Aaron
> >> >
> >> >
> >> > On Sat, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov <
> ekirpic...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Thanks. And how will n-net react?
> >> >>
> >> >>
> >> >>
> >> >> 18.08.2012, в 0:43, Aaron Rosen  написал(а):
> >> >>
> >> >> Hi Eugene,
> >> >>
> >> >> This means that if a VM stops it's DHCP client that nova-network will
> >> >> be
> >> >> aware of this since the VM will not attempt to renew it's DHCP lease.
> >> >>
> >> >> Aaron
> >> >>
> >> >> On Fri, Aug 17, 2012 at 5:58 PM, Eugene Kirpichov
> >> >> 
> >> >> wrote:
> >> >>>
> >> >>> Hi,
> >> >>>
> >> >>> The documentation
> >> >>>
> >> >>>
> >> >>>
> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-flat-dhcp-networking.html
> >> >>> has the passage: "The nova-network service will track leases and
> >> >>> releases in the database so it knows if a VM instance has stopped
> >> >>> properly configuring via DHCP"
> >> >>>
> >> >>> Can someone briefly explain me what this means, if possible with
> rough
> >> >>> pointers to code?
> >> >>> I don't recall nova noticing when my VM actually stopped properly
> >> >>> configuring via DHCP.
> >> >>>
> >> >>> --
> >> >>> Eugene Kirpichov
> >> >>> http://www.linkedin.com/in/eugenekirpichov
> >> >>>
> >> >>> ___
> >> >>> Mailing list: https://launchpad.net/~openstack
> >> >>> Post to : openstack@lists.launchpad.net
> >> >>> Unsubscribe : https://launchpad.net/~openstack
> >> >>> More help   : https://help.launchpad.net/ListHelp
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Eugene Kirpichov
> >> http://www.linkedin.com/in/eugenekirpichov
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : openstack@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~openstack
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
>
>
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov
>
___
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] Question about Flat DHCP networking

[Eugene Kirpichov]

Heh, that's an article by my colleague Piotr Siwczak, which I already
read very thouroughly during the review process - but thanks ;)

Actually I already found the answer to my question and added it to the
documentation (when the codereview is completed) - it was related to
nova-dhcpbridge script.

On Mon, Aug 20, 2012 at 10:21 PM, hitesh wadekar
 wrote:
> May be this article will help.
>
> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/
>
> Thanks,
> Hitesh
>
>
> On Tue, Aug 21, 2012 at 3:16 AM, Eugene Kirpichov 
> wrote:
>>
>> Hi,
>>
>> I found the code. It's a dnsmasq dhcp-script called by dnsmasq for
>> various events, it resides in nova/bin/nova-dhcpbridge and it, among
>> other things, calls release_fixed_ip when the lease expires.
>>
>> On Sat, Aug 18, 2012 at 1:01 AM, Aaron Rosen  wrote:
>> > Hi Eugene,
>> >
>> > I'm not sure I have not looked at the code (I'm guessing that it
>> > probably
>> > keeps the lease around since it knows the VM is still active instead of
>> > recycling the ip address). Though this is just a guess. You should look
>> > at
>> > the implementation details if you are curious.
>> >
>> > Aaron
>> >
>> >
>> > On Sat, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov 
>> > wrote:
>> >>
>> >> Thanks. And how will n-net react?
>> >>
>> >>
>> >>
>> >> 18.08.2012, в 0:43, Aaron Rosen  написал(а):
>> >>
>> >> Hi Eugene,
>> >>
>> >> This means that if a VM stops it's DHCP client that nova-network will
>> >> be
>> >> aware of this since the VM will not attempt to renew it's DHCP lease.
>> >>
>> >> Aaron
>> >>
>> >> On Fri, Aug 17, 2012 at 5:58 PM, Eugene Kirpichov
>> >> 
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> The documentation
>> >>>
>> >>>
>> >>> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-flat-dhcp-networking.html
>> >>> has the passage: "The nova-network service will track leases and
>> >>> releases in the database so it knows if a VM instance has stopped
>> >>> properly configuring via DHCP"
>> >>>
>> >>> Can someone briefly explain me what this means, if possible with rough
>> >>> pointers to code?
>> >>> I don't recall nova noticing when my VM actually stopped properly
>> >>> configuring via DHCP.
>> >>>
>> >>> --
>> >>> Eugene Kirpichov
>> >>> http://www.linkedin.com/in/eugenekirpichov
>> >>>
>> >>> ___
>> >>> Mailing list: https://launchpad.net/~openstack
>> >>> Post to : openstack@lists.launchpad.net
>> >>> Unsubscribe : https://launchpad.net/~openstack
>> >>> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Eugene Kirpichov
>> http://www.linkedin.com/in/eugenekirpichov
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>
>



-- 
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov

___
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] Question about Flat DHCP networking

[hitesh wadekar]

May be this article will help.

http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/


Thanks,
Hitesh

On Tue, Aug 21, 2012 at 3:16 AM, Eugene Kirpichov wrote:

> Hi,
>
> I found the code. It's a dnsmasq dhcp-script called by dnsmasq for
> various events, it resides in nova/bin/nova-dhcpbridge and it, among
> other things, calls release_fixed_ip when the lease expires.
>
> On Sat, Aug 18, 2012 at 1:01 AM, Aaron Rosen  wrote:
> > Hi Eugene,
> >
> > I'm not sure I have not looked at the code (I'm guessing that it probably
> > keeps the lease around since it knows the VM is still active instead of
> > recycling the ip address). Though this is just a guess. You should look
> at
> > the implementation details if you are curious.
> >
> > Aaron
> >
> >
> > On Sat, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov 
> > wrote:
> >>
> >> Thanks. And how will n-net react?
> >>
> >>
> >>
> >> 18.08.2012, в 0:43, Aaron Rosen  написал(а):
> >>
> >> Hi Eugene,
> >>
> >> This means that if a VM stops it's DHCP client that nova-network will be
> >> aware of this since the VM will not attempt to renew it's DHCP lease.
> >>
> >> Aaron
> >>
> >> On Fri, Aug 17, 2012 at 5:58 PM, Eugene Kirpichov  >
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> The documentation
> >>>
> >>>
> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-flat-dhcp-networking.html
> >>> has the passage: "The nova-network service will track leases and
> >>> releases in the database so it knows if a VM instance has stopped
> >>> properly configuring via DHCP"
> >>>
> >>> Can someone briefly explain me what this means, if possible with rough
> >>> pointers to code?
> >>> I don't recall nova noticing when my VM actually stopped properly
> >>> configuring via DHCP.
> >>>
> >>> --
> >>> Eugene Kirpichov
> >>> http://www.linkedin.com/in/eugenekirpichov
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~openstack
> >>> Post to : openstack@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~openstack
> >>> More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >
>
>
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] [Glance] Windows image password customize?

[한승진]

Hi

I'm studying how to regenerate or customize windows instance when the
instance boot. However, I cannot get an answer still now.

Linux image doesn't have to regenerate the password because of keyfile
login.

Do you have any idea ??
___
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] openstack libvirt lxc

[廖南海]

Who use the lxc virtual machine？
Please give me some advices?
I encountered some problems.
Thank you!
-- 
Never stop touch forever!
___
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] multiple LDAPs in OpenStack

[Dolph Mathews]

While there's no implementation of this in keystone today, I'm sure you
could write your own LDAP driver in keystone, heavily leveraging the
existing LDAP driver.

-Dolph

On Mon, Aug 20, 2012 at 4:19 PM, Ryan Lane  wrote:

> On Mon, Aug 20, 2012 at 1:52 PM, pat  wrote:
> > Hello,
> >
> > I'm new to this list and OpenStack at all. I want to ask a question: I
> want to
> > ask if it's possible to use one LDAP per tenant. I've searched the web,
> but
> > didn't found the answer.
> >
>
> In keystone this is not currently possible.
>
> - Ryan
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] sort_key and sort_dir for collections based REST APIs

[Dolph Mathews]

I have the majority of the latest v3 draft implemented on both the client
and server, but it's neither complete nor polished... yet.

My goal is to have a solid implementation (perhaps in a branch?) for
everyone to poke at in plenty of time for the summit :)

-Dolph

On Mon, Aug 20, 2012 at 4:33 PM, Gabriel Hurley
wrote:

> Given that the v3 API didn't get implemented in Folsom that gives us a
> perfect opportunity to talk about this stuff at the Grizzly summit! ;-)
>
> - Gabriel
>
> > -Original Message-
> > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> > [mailto:openstack-
> > bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> > Joseph Heck
> > Sent: Monday, August 20, 2012 1:45 PM
> > To: Brian Waldon
> > Cc: openstack@lists.launchpad.net
> > Subject: Re: [Openstack] sort_key and sort_dir for collections based REST
> > APIs
> >
> > In the V3 Keystone API, we asserted that we wanted filter functions, but
> > didn't go to the length of defining a "sort_key" and "sort_direction" in
> the
> > API spec.
> >
> > ref: https://docs.google.com/document/d/1VP-bTBbwsn6q-
> > rDzuS9CEKb2ubE1VjbWRFd4BkkjoOY/edit?pli=1
> >
> > -joe
> >
> > On Aug 20, 2012, at 10:05 AM, Brian Waldon  wrote:
> > > As we can't just add things to our APIs, it's not straight-forward to
> support
> > them across the board. I think it would make sense to bake these
> > parameters into the next versions of our APIs for collection sorting,
> but my
> > opinion is definitely biased.
> > >
> > > Maybe Joe Heck can comment, as he's working on the v2 Identity API.
> > >
> > > Brian
> > >
> > >
> > > On Aug 20, 2012, at 11:43 AM, boden wrote:
> > >
> > >> All,
> > >> Is anybody here familiar with the 'sort_key' and 'sort_dir'
> > >> parameters for collection based APIs?
> > >>
> > >> Specifically I'm wondering if there are any plans to add support for
> > >> these 2 params across the board (all collections based REST APIs
> > >> including the 'primary compute extensions')? Based on my
> > >> google-ability it appears they are only on the glance image APIs
> > >> (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
> > >> present moment, so looking for more clarity on this topic
> > >> intermediate to longer term.
> > >>
> > >> Thanks much
> > >>
> > >>
> > >>
> > >> ___
> > >> Mailing list: https://launchpad.net/~openstack
> > >> Post to : 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
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] Question about Flat DHCP networking

[Eugene Kirpichov]

Hi,

I found the code. It's a dnsmasq dhcp-script called by dnsmasq for
various events, it resides in nova/bin/nova-dhcpbridge and it, among
other things, calls release_fixed_ip when the lease expires.

On Sat, Aug 18, 2012 at 1:01 AM, Aaron Rosen  wrote:
> Hi Eugene,
>
> I'm not sure I have not looked at the code (I'm guessing that it probably
> keeps the lease around since it knows the VM is still active instead of
> recycling the ip address). Though this is just a guess. You should look at
> the implementation details if you are curious.
>
> Aaron
>
>
> On Sat, Aug 18, 2012 at 3:48 AM, Eugene Kirpichov 
> wrote:
>>
>> Thanks. And how will n-net react?
>>
>>
>>
>> 18.08.2012, в 0:43, Aaron Rosen  написал(а):
>>
>> Hi Eugene,
>>
>> This means that if a VM stops it's DHCP client that nova-network will be
>> aware of this since the VM will not attempt to renew it's DHCP lease.
>>
>> Aaron
>>
>> On Fri, Aug 17, 2012 at 5:58 PM, Eugene Kirpichov 
>> wrote:
>>>
>>> Hi,
>>>
>>> The documentation
>>>
>>> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-flat-dhcp-networking.html
>>> has the passage: "The nova-network service will track leases and
>>> releases in the database so it knows if a VM instance has stopped
>>> properly configuring via DHCP"
>>>
>>> Can someone briefly explain me what this means, if possible with rough
>>> pointers to code?
>>> I don't recall nova noticing when my VM actually stopped properly
>>> configuring via DHCP.
>>>
>>> --
>>> Eugene Kirpichov
>>> http://www.linkedin.com/in/eugenekirpichov
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>



-- 
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov

___
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] sort_key and sort_dir for collections based REST APIs

[Gabriel Hurley]

Given that the v3 API didn't get implemented in Folsom that gives us a perfect 
opportunity to talk about this stuff at the Grizzly summit! ;-)

- Gabriel

> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> Joseph Heck
> Sent: Monday, August 20, 2012 1:45 PM
> To: Brian Waldon
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] sort_key and sort_dir for collections based REST
> APIs
> 
> In the V3 Keystone API, we asserted that we wanted filter functions, but
> didn't go to the length of defining a "sort_key" and "sort_direction" in the
> API spec.
> 
> ref: https://docs.google.com/document/d/1VP-bTBbwsn6q-
> rDzuS9CEKb2ubE1VjbWRFd4BkkjoOY/edit?pli=1
> 
> -joe
> 
> On Aug 20, 2012, at 10:05 AM, Brian Waldon  wrote:
> > As we can't just add things to our APIs, it's not straight-forward to 
> > support
> them across the board. I think it would make sense to bake these
> parameters into the next versions of our APIs for collection sorting, but my
> opinion is definitely biased.
> >
> > Maybe Joe Heck can comment, as he's working on the v2 Identity API.
> >
> > Brian
> >
> >
> > On Aug 20, 2012, at 11:43 AM, boden wrote:
> >
> >> All,
> >> Is anybody here familiar with the 'sort_key' and 'sort_dir'
> >> parameters for collection based APIs?
> >>
> >> Specifically I'm wondering if there are any plans to add support for
> >> these 2 params across the board (all collections based REST APIs
> >> including the 'primary compute extensions')? Based on my
> >> google-ability it appears they are only on the glance image APIs
> >> (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
> >> present moment, so looking for more clarity on this topic
> >> intermediate to longer term.
> >>
> >> Thanks much
> >>
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~openstack
> >> Post to : 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



___
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] multiple LDAPs in OpenStack

[Ryan Lane]

On Mon, Aug 20, 2012 at 1:52 PM, pat  wrote:
> Hello,
>
> I'm new to this list and OpenStack at all. I want to ask a question: I want to
> ask if it's possible to use one LDAP per tenant. I've searched the web, but
> didn't found the answer.
>

In keystone this is not currently possible.

- Ryan

___
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] multiple LDAPs in OpenStack

[pat]

Hello,

I'm new to this list and OpenStack at all. I want to ask a question: I want to
ask if it's possible to use one LDAP per tenant. I've searched the web, but
didn't found the answer.

Thanks

 Pat


Freehosting PIPNI - http://www.pipni.cz/


___
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] sort_key and sort_dir for collections based REST APIs

[Joseph Heck]

In the V3 Keystone API, we asserted that we wanted filter functions, but didn't 
go to the length of defining a "sort_key" and "sort_direction" in the API spec.

ref: 
https://docs.google.com/document/d/1VP-bTBbwsn6q-rDzuS9CEKb2ubE1VjbWRFd4BkkjoOY/edit?pli=1

-joe

On Aug 20, 2012, at 10:05 AM, Brian Waldon  wrote:
> As we can't just add things to our APIs, it's not straight-forward to support 
> them across the board. I think it would make sense to bake these parameters 
> into the next versions of our APIs for collection sorting, but my opinion is 
> definitely biased. 
> 
> Maybe Joe Heck can comment, as he's working on the v2 Identity API.
> 
> Brian
> 
> 
> On Aug 20, 2012, at 11:43 AM, boden wrote:
> 
>> All,
>> Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
>> for collection based APIs?
>> 
>> Specifically I'm wondering if there are any plans to add support for
>> these 2 params across the board (all collections based REST APIs
>> including the 'primary compute extensions')? Based on my google-ability
>> it appears they are only on the glance image APIs
>> (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
>> present moment, so looking for more clarity on this topic intermediate
>> to longer term.
>> 
>> Thanks much
>> 
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : 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] [openstack-dev] [Glance] Implementing Common Image Properties

[Gabe Westmaas]

It would definitely be great to see these as generally accepted properties.  In 
general, I would hope that anything that is accepted by the community 
eventually makes it into core API, and shipping with them on by default is a 
great first step.  Mostly, I'd like to see us able to turn off the 
"org.openstack__1__" part of the properties, if everyone agrees they are useful 
:)

Also just to highlight one of the links in the mailing list discussions, this 
is where we pulled those properties from: 
http://wiki.openstack.org/CommonImageProperties

Gabe

From: Brian Waldon mailto:bcwal...@gmail.com>>
Reply-To: OpenStack List 
mailto:openstack-...@lists.openstack.org>>
Date: Mon, 20 Aug 2012 14:11:20 -0400
To: "openstack@lists.launchpad.net" 
mailto:openstack@lists.launchpad.net>>, 
OpenStack List 
mailto:openstack-...@lists.openstack.org>>
Subject: [openstack-dev] [Glance] Implementing Common Image Properties

We discussed a common set of image properties a while back on the mailing list 
([1] and [2]). The general idea was to define a common way to expose useful 
image properties (distro, version, architecture, packages, etc).

It doesn't appear we ever came to a hard consensus, but Rackspace has been 
publishing the following properties in their deployment:

org.openstack__1__architecture = x64
org.openstack__1__os_distro = org.ubuntu
org.openstack__1__os_version = 12.04

If the idea is to get all deployments to publish these properties, I think what 
Rackspace has implemented would be a good starting point. The question I want 
to pose to the community is this:

Does it make sense to ship a set of JSON schemas with Glance that represent 
these properties? Doing so wouldn't explicitly require all deployments to use 
them, but it would reduce the work required to publish them and help ensure 
they have a common meaning across deployments. Keep in mind that we would be 
shipping these as a part of Glance, not as a part of the Images API spec.

I personally think it would be great to provide these, and to do so in the 
Folsom release so those deployers riding major releases wouldn't be left out in 
the dark.

All comments welcome!

Brian Waldon


[1] http://markmail.org/message/5bd5zkyre57ppi3n
[2] http://markmail.org/message/soaldxs4lovd2uir
___ OpenStack-dev mailing list 
openstack-...@lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
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] Floating IPs and multiple NICs

[Juris]

Greetings everyone,

Just a quick question.
Is it possible to assign floating IPs to multiple nova node interfaces?
For instance if I have a server with 4 NICs and I'd like to use NIC1
for private network, NIC2 for data and management, NIC3 for one of my
public IP subnets and NIC4 for another public IP subnet?

___
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] Floating IPs and multiple NICs

[Juris]

Greetings everyone,

Just a quick question.
Is it possible to assign floating IPs to multiple nova node interfaces?
For instance if I have a server with 4 NICs and I'd like to use NIC1
for private network, NIC2 for data and management, NIC3 for one of my
public IP subnets and NIC4 for another public IP subnet?

___
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] sort_key and sort_dir for collections based REST APIs

[Matt Joyce]

+10

On Mon, Aug 20, 2012 at 11:42 AM, Gabriel Hurley
wrote:

> For two summits running I've been advocating the need for a common
> standard of functionality for all OpenStack APIs (things like sorting, bulk
> operations, filtering, pagination, etc.). I intend to push on the issue
> even harder this time around at the Grizzly summit (I'm going to propose an
> entire working session on it).
>
> It's one of those problems that simply *cannot* be solved one project at a
> time. The community needs to agree, and then the projects need to implement
> the solutions over time.
>
>   - Gabriel
>
> > -Original Message-
> > From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> > [mailto:openstack-
> > bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> > Brian Waldon
> > Sent: Monday, August 20, 2012 10:06 AM
> > To: boden
> > Cc: openstack@lists.launchpad.net
> > Subject: Re: [Openstack] sort_key and sort_dir for collections based REST
> > APIs
> >
> > As we can't just add things to our APIs, it's not straight-forward to
> support
> > them across the board. I think it would make sense to bake these
> > parameters into the next versions of our APIs for collection sorting,
> but my
> > opinion is definitely biased.
> >
> > Maybe Joe Heck can comment, as he's working on the v2 Identity API.
> >
> > Brian
> >
> >
> > On Aug 20, 2012, at 11:43 AM, boden wrote:
> >
> > > All,
> > > Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
> > > for collection based APIs?
> > >
> > > Specifically I'm wondering if there are any plans to add support for
> > > these 2 params across the board (all collections based REST APIs
> > > including the 'primary compute extensions')? Based on my
> > > google-ability it appears they are only on the glance image APIs
> > > (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
> > > present moment, so looking for more clarity on this topic intermediate
> > > to longer term.
> > >
> > > Thanks much
> > >
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~openstack
> > > Post to : 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
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] AWS CreateImage compat

[Jorge Niedbalski]

Hello Eoghan,

On Wed, Jul 25, 2012 at 5:38 AM, Eoghan Glynn  wrote:
>
>
> Hi Jorge,
>
> What version are you testing against?

Essex

>
> I recently got a series of patches onto master that addressed a bunch
> of issues in the EC2 CreateImage support, so that it now works smoothly
> with volume-backed nova instances:
>
>   https://review.openstack.org/9732
>   https://review.openstack.org/9833
>   https://review.openstack.org/9915
>   https://review.openstack.org/9925
>   https://review.openstack.org/9715
>
> This functionality is tested with a new devstack exercise, awaiting
> approval:
>
>   https://review.openstack.org/9853
>
> Also, I have backported the patches to stable/essex where they await
> review:
>
>   https://review.openstack.org/10224
>   https://review.openstack.org/10225
>   https://review.openstack.org/10226
>   https://review.openstack.org/10228
>   https://review.openstack.org/10230
>   https://review.openstack.org/10238
>

I am gonna test this patchset with boto.

> Cheers,
> Eoghan


Thanks you the work!


Jorge Niedbalski R.
--

___
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] sort_key and sort_dir for collections based REST APIs

[Gabriel Hurley]

For two summits running I've been advocating the need for a common standard of 
functionality for all OpenStack APIs (things like sorting, bulk operations, 
filtering, pagination, etc.). I intend to push on the issue even harder this 
time around at the Grizzly summit (I'm going to propose an entire working 
session on it).

It's one of those problems that simply *cannot* be solved one project at a 
time. The community needs to agree, and then the projects need to implement the 
solutions over time.

  - Gabriel

> -Original Message-
> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
> [mailto:openstack-
> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of
> Brian Waldon
> Sent: Monday, August 20, 2012 10:06 AM
> To: boden
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] sort_key and sort_dir for collections based REST
> APIs
> 
> As we can't just add things to our APIs, it's not straight-forward to support
> them across the board. I think it would make sense to bake these
> parameters into the next versions of our APIs for collection sorting, but my
> opinion is definitely biased.
> 
> Maybe Joe Heck can comment, as he's working on the v2 Identity API.
> 
> Brian
> 
> 
> On Aug 20, 2012, at 11:43 AM, boden wrote:
> 
> > All,
> > Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
> > for collection based APIs?
> >
> > Specifically I'm wondering if there are any plans to add support for
> > these 2 params across the board (all collections based REST APIs
> > including the 'primary compute extensions')? Based on my
> > google-ability it appears they are only on the glance image APIs
> > (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
> > present moment, so looking for more clarity on this topic intermediate
> > to longer term.
> >
> > Thanks much
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : 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



___
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] [Glance] Implementing Common Image Properties

[Brian Waldon]

We discussed a common set of image properties a while back on the mailing list 
([1] and [2]). The general idea was to define a common way to expose useful 
image properties (distro, version, architecture, packages, etc). 

It doesn't appear we ever came to a hard consensus, but Rackspace has been 
publishing the following properties in their deployment:

org.openstack__1__architecture = x64   
org.openstack__1__os_distro = org.ubuntu
org.openstack__1__os_version = 12.04

If the idea is to get all deployments to publish these properties, I think what 
Rackspace has implemented would be a good starting point. The question I want 
to pose to the community is this:

Does it make sense to ship a set of JSON schemas with Glance that represent 
these properties? Doing so wouldn't explicitly require all deployments to use 
them, but it would reduce the work required to publish them and help ensure 
they have a common meaning across deployments. Keep in mind that we would be 
shipping these as a part of Glance, not as a part of the Images API spec.

I personally think it would be great to provide these, and to do so in the 
Folsom release so those deployers riding major releases wouldn't be left out in 
the dark.

All comments welcome!

Brian Waldon


[1] http://markmail.org/message/5bd5zkyre57ppi3n
[2] http://markmail.org/message/soaldxs4lovd2uir___
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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Chuck Short]

Hi,

Yes, they are safe to use and they are production ready.

regards
chuck

On Sun, 19 Aug 2012 20:20:18 +0800
Ji Zhang  wrote:

> Hi,
> 
> I'm to deploy OpenStack Essex in production environment. According to
> the official manual, I should either install it manually or use
> dodai-deploy. After briefly browsing these methods, it seems that both
> of them are using the packages distributed in official repository
> (i.e. apt-get install keystone), not building from source like
> DevStack does.
> 
> So my question is, as is said in the title, are these packages
> production ready? Or should I checkout the stable/essex branch of each
> project and build it by myself?
> 
> Thanks.
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Joshua Harlow]

I'm working on making anvil build packages (at least basic ones).

My idea is that since it will somewhat track how to
setup/uninstall/configure (along with it knowing how to map pip packages
to distribution packages, something being helped by the new more complete
pip-requires lists) an openstack release that it should also be able to
package (for at least rhel/ubuntu).

Its a WIP... 

Feel free to help ;)

http://anvil.readthedocs.org/en/latest/topics/features.html

This list might be useful anyway:
https://github.com/yahoo/Openstack-Anvil/blob/master/conf/distros/rhel-6.ya
ml#L73 (yes I know I killed ubuntu, only so much time in the day, will get
that back in shape soon).

-Josh

On 8/19/12 5:20 AM, "Ji Zhang"  wrote:

>Hi,
>
>I'm to deploy OpenStack Essex in production environment. According to
>the official manual, I should either install it manually or use
>dodai-deploy. After briefly browsing these methods, it seems that both
>of them are using the packages distributed in official repository
>(i.e. apt-get install keystone), not building from source like
>DevStack does.
>
>So my question is, as is said in the title, are these packages
>production ready? Or should I checkout the stable/essex branch of each
>project and build it by myself?
>
>Thanks.
>
>___
>Mailing list: https://launchpad.net/~openstack
>Post to : 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] sort_key and sort_dir for collections based REST APIs

[Brian Waldon]

As we can't just add things to our APIs, it's not straight-forward to support 
them across the board. I think it would make sense to bake these parameters 
into the next versions of our APIs for collection sorting, but my opinion is 
definitely biased. 

Maybe Joe Heck can comment, as he's working on the v2 Identity API.

Brian


On Aug 20, 2012, at 11:43 AM, boden wrote:

> All,
> Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
> for collection based APIs?
> 
> Specifically I'm wondering if there are any plans to add support for
> these 2 params across the board (all collections based REST APIs
> including the 'primary compute extensions')? Based on my google-ability
> it appears they are only on the glance image APIs
> (http://docs.openstack.org/developer/glance/glanceapi.html ) at the
> present moment, so looking for more clarity on this topic intermediate
> to longer term.
> 
> Thanks much
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] Floating IPs and multiple NICs

[Juris]

Greetings everyone,

Just a quick question.
Is it possible to assign floating IPs to multiple nova node interfaces?
For instance if I have a server with 4 NICs and I'd like to use NIC1
for private network, NIC2 for data and management, NIC3 for one of my
public IP subnets and NIC4 for another public IP subnet?

Best wishes,
Juris

___
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] sort_key and sort_dir for collections based REST APIs

[boden]

All,
Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
for collection based APIs?

Specifically I'm wondering if there are any plans to add support for
these 2 params across the board (all collections based REST APIs
including the 'primary compute extensions')? Based on my google-ability
it appears they are only on the glance image APIs
(http://docs.openstack.org/developer/glance/glanceapi.html ) at the
present moment, so looking for more clarity on this topic intermediate
to longer term.

Thanks much



___
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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Jonathan D. Proulx]

Hi All,

Dave and Marek  both have good points.  But I have to say I'm more
with Dave on this one.

OpenStack is still moving very fast so two month is a long time, but
if the version in you distro isn't ready for production for you then OpenStack
isn't ready for production for you unless you have a substantial
internal Dev/Ops support team for it.

Managing something as complicated as Openstack with all of it's sub
parts and external dependencies with all it's sub projects directly
fro "upstream" source repo and then tracking and validating updates is
not a manageable solution.  

My recommendation would be to use Precise/Essex and test it to see
that it does what you need.   I use this combo for an interanal cloud
and I also have the sense from this list and speaking with other
moderate to large scale users that this is a very common production
combination. 

If you find issues in the packages version that are fixed in teh git
repo than you can weigh an actual need against the significant added
complexity.  

-Jon


signature.asc
Description: Digital 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

[Openstack] VM's naming pattern.

[Vladimir Glafirov]

Hi all.

I just wondering. Is there any way to specify virtual machines naming
pattern in openstack. Let's presume I would need to create ten vm's with
web##-dev names and 10 vm's with web##-prod names.
If I specify number of instances in dashboard it name N instances with a
same name.

Thank you for your answer,
Vladimir Glafirov

___
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] keystone initialization problem

[Xin Zhao]

Thanks all for the suggestions, it helped to trace to the real problem: 
our own proxy server is misconfigured, nothing to do with openstack.

After fixing proxy server, it works.

Thanks,
Xin

On 8/17/2012 6:28 PM, Adam Young wrote:

OK, SERVICE_TOKEN is the same as --token


You can follow the steps here:

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_OpenStack_Preview/


Specifically:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_OpenStack_Preview/1/html/Getting_Started_Guide/ch02.html#id3165390
||  *|export SERVICE_TOKEN=$(openssl rand -hex 10)|*
||  *|export SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0|*
||  *|echo $SERVICE_TOKEN > /tmp/ks_admin_token|*
||  *|sudo openstack-config --set /etc/keystone/keystone.conf \|*
   *|DEFAULT admin_token $SERVICE_TOKEN|*


and that should be the admin_token value that you have.

If nothing is in the log, it probably means you have not actually hit 
the right server.




On 08/17/2012 05:47 PM, Dolph Mathews wrote:
The admin_token value from keystone.conf is not a real token; it 
exists as a string in memory and has no context, user or actual roles 
associated with it (hence it does not appear in your token table).


As for your actual issue, I don't see anything obviously wrong with 
what's below. Is logging enabled & working, otherwise? Have you tried 
"verbose = True" and "debug = True"? Have you tried running that 
command from the compute node itself, rather than over the internet 
IP? What happens when you curl / GET / whatever http://of the controller node>:35357/v2.0 and/or http://127.0.0.1:35357/v2.0 ?


-Dolph

On Fri, Aug 17, 2012 at 3:26 PM, Xin Zhao > wrote:


Hello,

I newly install keystone on the RHEL6 machine, but it is not
working. The following command fails:

$ keystone --token 
--endpoint http://:35357/v2.0
tenant-create --name openstackDemo --description "Default Tenant"
--enabled true

Unable to communicate with identity service: (403, 'Forbidden').
(HTTP 400)

There is no relevant log in the keystone.log file.

Here is the instruction I follow:

http://docs.openstack.org/essex/openstack-compute/install/yum/content/setting-up-tenants-users-and-roles.html

This is done on the controller node itself. I can telnet to
:35357. I can also
log into mysql DB as keystone user, although there is no
 entry in any of the keystone tables.

Any idea what is going wrong here?

Thanks,
Xin


___
Mailing list: https://launchpad.net/~openstack

Post to : 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




___
Mailing list: https://launchpad.net/~openstack
Post to : 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] Keystone Folsom-3 git based installation failure.

[Bekir Dogan]

Hi;

Do you have pyhon-dev package installed?

bekir

On Mon, Aug 20, 2012 at 2:40 PM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:

> Hi-
>
> I have downloaded the source code from https://launchpad.net/keystone/.
>
>
> When I execute the command, " pip install -r tools/pip-requires ", I
> seeing the following errors.
>
> Please help me resolve the issue.
>
>
>
> root@openstackController:/home/localadmin/Desktop/openstackfolsom3/keystone-2012.2#
> pip install -r tools/pip-requires
> Downloading/unpacking pam==0.1.4 (from -r tools/pip-requires (line 2))
>   Cannot fetch index base URL http://pypi.python.org/simple/
>   Downloading pam-0.1.4.tar.gz
>   Running setup.py egg_info for package pam
>
> Downloading/unpacking WebOb==1.0.8 (from -r tools/pip-requires (line 3))
>   Downloading WebOb-1.0.8.zip (194Kb): 194Kb downloaded
>   Running setup.py egg_info for package WebOb
>
> no previously-included directories found matching '*.pyc'
> no previously-included directories found matching '*.pyo'
> Downloading/unpacking eventlet (from -r tools/pip-requires (line 4))
>   Downloading eventlet-0.9.17.tar.gz (262Kb): 262Kb downloaded
>   Running setup.py egg_info for package eventlet
>
> Downloading/unpacking greenlet (from -r tools/pip-requires (line 5))
>   Downloading greenlet-0.4.0.zip (72Kb): 72Kb downloaded
>   Running setup.py egg_info for package greenlet
>
> Downloading/unpacking PasteDeploy (from -r tools/pip-requires (line 6))
>   Downloading PasteDeploy-1.5.0.tar.gz
>   Running setup.py egg_info for package PasteDeploy
>
> Downloading/unpacking paste (from -r tools/pip-requires (line 7))
>   Downloading Paste-1.7.5.1.tar.gz (523Kb): 523Kb downloaded
>   Running setup.py egg_info for package paste
>
> warning: no previously-included files matching '*' found under
> directory 'docs/_build/_sources'
> Downloading/unpacking routes (from -r tools/pip-requires (line 8))
>   Downloading Routes-1.13.tar.gz (797Kb): 797Kb downloaded
>   Running setup.py egg_info for package routes
>
> warning: no previously-included files matching '.DS_Store' found
> anywhere in distribution
> warning: no previously-included files matching '*.hgignore' found
> anywhere in distribution
> warning: no previously-included files matching '*.hgtags' found
> anywhere in distribution
> Downloading/unpacking sqlalchemy (from -r tools/pip-requires (line 9))
>   Downloading SQLAlchemy-0.7.8.tar.gz (2.6Mb): 2.6Mb downloaded
>   Running setup.py egg_info for package sqlalchemy
>
> warning: no files found matching '*.jpg' under directory 'doc'
> no previously-included directories found matching 'doc/build/output'
> Downloading/unpacking sqlalchemy-migrate (from -r tools/pip-requires (line
> 10))
>   Downloading sqlalchemy-migrate-0.7.2.tar.gz (105Kb): 105Kb downloaded
>   Running setup.py egg_info for package sqlalchemy-migrate
>
> warning: no files found matching '*' under directory 'tests'
> warning: no previously-included files matching '*pyc' found anywhere
> in distribution
> warning: no previously-included files found matching '.hgtags'
> warning: no previously-included files matching '*' found under
> directory 'docs/_build'
> Downloading/unpacking passlib (from -r tools/pip-requires (line 11))
>   Downloading passlib-1.6.1.tar.gz (395Kb): 395Kb downloaded
>   Running setup.py egg_info for package passlib
>
> warning: no files found matching 'passlib/*.cfg'
> no previously-included directories found matching '*.komodoproject'
> Requirement already satisfied (use --upgrade to upgrade): lxml in
> /usr/lib/python2.7/dist-packages (from -r tools/pip-requires (line 12))
> Downloading/unpacking iso8601>=0.1.4 (from -r tools/pip-requires (line 13))
>   Downloading iso8601-0.1.4.tar.gz
>   Running setup.py egg_info for package iso8601
>
> Downloading/unpacking repoze.lru>=0.3 (from routes->-r tools/pip-requires
> (line 8))
>   Downloading repoze.lru-0.6.tar.gz
>   Running setup.py egg_info for package repoze.lru
>
> Downloading/unpacking decorator (from sqlalchemy-migrate->-r
> tools/pip-requires (line 10))
>   Downloading decorator-3.3.3.tar.gz
>   Running setup.py egg_info for package decorator
>
> warning: no previously-included files found matching 'Makefile'
> Downloading/unpacking Tempita>=0.4 (from sqlalchemy-migrate->-r
> tools/pip-requires (line 10))
>   Downloading Tempita-0.5.1.tar.gz
>   Running setup.py egg_info for package Tempita
>
> Requirement already satisfied (use --upgrade to upgrade): distribute in
> /usr/lib/python2.7/dist-packages (from sqlalchemy-migrate->-r
> tools/pip-requires (line 10))
> Installing collected packages: pam, WebOb, eventlet, greenlet,
> PasteDeploy, paste, routes, sqlalchemy, sqlalchemy-migrate, passlib,
> iso8601, repoze.lru, decorator, Tempita
>   Found existing installation: PAM 0.4.2
> Uninstalling PAM:
>   Successfully uninstalled PAM
>   Running setup.py install for pam
>
>   Running setup.py install for WebOb
>
> n

[Openstack] Keystone Folsom-3 git based installation failure.

[Trinath Somanchi]

Hi-

I have downloaded the source code from https://launchpad.net/keystone/.


When I execute the command, " pip install -r tools/pip-requires ", I seeing
the following errors.

Please help me resolve the issue.



root@openstackController:/home/localadmin/Desktop/openstackfolsom3/keystone-2012.2#
pip install -r tools/pip-requires
Downloading/unpacking pam==0.1.4 (from -r tools/pip-requires (line 2))
  Cannot fetch index base URL http://pypi.python.org/simple/
  Downloading pam-0.1.4.tar.gz
  Running setup.py egg_info for package pam

Downloading/unpacking WebOb==1.0.8 (from -r tools/pip-requires (line 3))
  Downloading WebOb-1.0.8.zip (194Kb): 194Kb downloaded
  Running setup.py egg_info for package WebOb

no previously-included directories found matching '*.pyc'
no previously-included directories found matching '*.pyo'
Downloading/unpacking eventlet (from -r tools/pip-requires (line 4))
  Downloading eventlet-0.9.17.tar.gz (262Kb): 262Kb downloaded
  Running setup.py egg_info for package eventlet

Downloading/unpacking greenlet (from -r tools/pip-requires (line 5))
  Downloading greenlet-0.4.0.zip (72Kb): 72Kb downloaded
  Running setup.py egg_info for package greenlet

Downloading/unpacking PasteDeploy (from -r tools/pip-requires (line 6))
  Downloading PasteDeploy-1.5.0.tar.gz
  Running setup.py egg_info for package PasteDeploy

Downloading/unpacking paste (from -r tools/pip-requires (line 7))
  Downloading Paste-1.7.5.1.tar.gz (523Kb): 523Kb downloaded
  Running setup.py egg_info for package paste

warning: no previously-included files matching '*' found under
directory 'docs/_build/_sources'
Downloading/unpacking routes (from -r tools/pip-requires (line 8))
  Downloading Routes-1.13.tar.gz (797Kb): 797Kb downloaded
  Running setup.py egg_info for package routes

warning: no previously-included files matching '.DS_Store' found
anywhere in distribution
warning: no previously-included files matching '*.hgignore' found
anywhere in distribution
warning: no previously-included files matching '*.hgtags' found
anywhere in distribution
Downloading/unpacking sqlalchemy (from -r tools/pip-requires (line 9))
  Downloading SQLAlchemy-0.7.8.tar.gz (2.6Mb): 2.6Mb downloaded
  Running setup.py egg_info for package sqlalchemy

warning: no files found matching '*.jpg' under directory 'doc'
no previously-included directories found matching 'doc/build/output'
Downloading/unpacking sqlalchemy-migrate (from -r tools/pip-requires (line
10))
  Downloading sqlalchemy-migrate-0.7.2.tar.gz (105Kb): 105Kb downloaded
  Running setup.py egg_info for package sqlalchemy-migrate

warning: no files found matching '*' under directory 'tests'
warning: no previously-included files matching '*pyc' found anywhere in
distribution
warning: no previously-included files found matching '.hgtags'
warning: no previously-included files matching '*' found under
directory 'docs/_build'
Downloading/unpacking passlib (from -r tools/pip-requires (line 11))
  Downloading passlib-1.6.1.tar.gz (395Kb): 395Kb downloaded
  Running setup.py egg_info for package passlib

warning: no files found matching 'passlib/*.cfg'
no previously-included directories found matching '*.komodoproject'
Requirement already satisfied (use --upgrade to upgrade): lxml in
/usr/lib/python2.7/dist-packages (from -r tools/pip-requires (line 12))
Downloading/unpacking iso8601>=0.1.4 (from -r tools/pip-requires (line 13))
  Downloading iso8601-0.1.4.tar.gz
  Running setup.py egg_info for package iso8601

Downloading/unpacking repoze.lru>=0.3 (from routes->-r tools/pip-requires
(line 8))
  Downloading repoze.lru-0.6.tar.gz
  Running setup.py egg_info for package repoze.lru

Downloading/unpacking decorator (from sqlalchemy-migrate->-r
tools/pip-requires (line 10))
  Downloading decorator-3.3.3.tar.gz
  Running setup.py egg_info for package decorator

warning: no previously-included files found matching 'Makefile'
Downloading/unpacking Tempita>=0.4 (from sqlalchemy-migrate->-r
tools/pip-requires (line 10))
  Downloading Tempita-0.5.1.tar.gz
  Running setup.py egg_info for package Tempita

Requirement already satisfied (use --upgrade to upgrade): distribute in
/usr/lib/python2.7/dist-packages (from sqlalchemy-migrate->-r
tools/pip-requires (line 10))
Installing collected packages: pam, WebOb, eventlet, greenlet, PasteDeploy,
paste, routes, sqlalchemy, sqlalchemy-migrate, passlib, iso8601,
repoze.lru, decorator, Tempita
  Found existing installation: PAM 0.4.2
Uninstalling PAM:
  Successfully uninstalled PAM
  Running setup.py install for pam

  Running setup.py install for WebOb

no previously-included directories found matching '*.pyc'
no previously-included directories found matching '*.pyo'
  Running setup.py install for eventlet

  Running setup.py install for greenlet
building 'greenlet' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fPIC -I/usr/include/

Re: [Openstack] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Ruzicka, Marek]

Don't get me wrong Dave,
I'm pretty sure, that you guys at Ubuntu are doing a lot for the sake of this 
project. I definitely didn't any mean disrespect.

On the other hand, I simply stay behind my statement... from my point of view 
it is not production ready.
Production readiness highly depends on the particular use case.
We are running very small environment which e.g. requires auto assigning of 
floating IPs. Version in repos does not include some fixes that are crucial for 
this. 
Considering the fixes were committed/merged few days after the current packages 
were published, it is understandable, but it doesn't change the fact, that it 
is not usable for me.

I see your point Dave. It probably wasn't "kosher" to answer general question 
with regards to my particular (very specific) experiences/needs. Even more I 
totally missed the "is it safe" part, and my statement could have been 
misinterpreted. 

Having you already here... when can we expect new version of packages? It would 
save me considerable effort if I could just wait few days and get the fixes 
from repos, rather than going for sources.

Regards,

Marek Ruzicka 
System Engineer (Storage)
T-Systems Slovakia s.r.o.
www.t-systems.sk 


-Original Message-
From: Dave Walker [mailto:dave.wal...@canonical.com] 
Sent: 20. augusta 2012 11:57
To: Ruzicka, Marek
Cc: zhangj...@gmail.com; openstack@lists.launchpad.net
Subject: Re: [Openstack] Is It Safe to Use The OpenStack Packages Distributed 
in Ubuntu 12.04 Official Repository?

>> - Reply message -
>> From: "Ji Zhang" 
>> To: "openstack@lists.launchpad.net" 
>> Subject: [Openstack] Is It Safe to Use The OpenStack Packages Distributed in 
>> Ubuntu 12.04 Official Repository?
>> Date: Mon, Aug 20, 2012 04:58
>> 
>> 
>> 
>> Hi,
>> 
>> I'm to deploy OpenStack Essex in production environment. According to 
>> the official manual, I should either install it manually or use 
>> dodai-deploy. After briefly browsing these methods, it seems that 
>> both of them are using the packages distributed in official 
>> repository (i.e. apt-get install keystone), not building from source 
>> like DevStack does.
>> 
>> So my question is, as is said in the title, are these packages 
>> production ready? Or should I checkout the stable/essex branch of 
>> each project and build it by myself?
>> 
>> Thanks.
>> 
>
>On Mon, Aug 20, 2012 at 08:53:23AM +0200, Ruzicka, Marek wrote:
> Hi,
> 
> Guys around will probably disagree,but I have spent last 5-6weeks 
> creating POC using repos is ubuntu, and I have to say it is not 
> production rdy yet.
> 
> Versions in repos are about 2months old if I'm not mistaken...too old 
> for such fast paced project.
> 
> Marek Ruzicka
> System Engineer (storage)
> T-Systems Slovakia s.r.o.
> 
> Sent from my mobile, please excuse typos.

Hi,

Hmm, I do disagree with this stance.  There are 3 issues being mingled 
together, but do have overlap.

1. Is it 'safe' for production.
   - All distributions commit to an assurance level of software they
 ship.  This differs between distributions, and the level of the
 assurance.  However, you can be pretty sure - that any major
 distro will be taking great care of their openstack packages.
   - In relation to Ubuntu, by using the distribution packages you can
 be assured that:
 - Security updates will be included promptly, usually on the day
   the embargo is lifted.
 - Assurance that the software has been tested in given scenarios
   with the dependencies and libraries that are shipped.  Any
   distribution will tell you that a project such as this, the
   core software is only half of the complexity, the dependencies
   carry significant burden.
 - Safe upgrade for security and bug fixes for the release, and
   reasonably easy transition between major versions.  A git
   checkout, doesn't promise safe upgrade.
   - With these factors taken into account, unless significant
 investment into controlling these issues on your own deployment,
 i'd consider it *un-safe* to use anything other than a
 distributions packages.

2. How current are the packages?
   - As mentioned in Marek's email, the packages are about 2 months
 old.  Originally, 12.04 released with Essex Final and some local
 distro patches.  The patches were incorporated upstream, and many
 others contributed fixes.  For this reason, we undertook the
 process of a Stable Release Update.  Due to the level of upstream
 CI, Ubuntu CI and further extended testing, we were able to
 release a snapshot, which seems to have proved to have been
 regression free (!).  This is a testament to the amount of
 pre-release work that went into this update.
   - We are currently preparing the next update, based on Essex
 Stable, which will undergo the same level of care, and should hit
 a mirror near you in a timely manner.
   - For a *stable* release of both upstream, and the distribut

Re: [Openstack] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Dave Walker]

>> - Reply message -
>> From: "Ji Zhang" 
>> To: "openstack@lists.launchpad.net" 
>> Subject: [Openstack] Is It Safe to Use The OpenStack Packages Distributed in 
>> Ubuntu 12.04 Official Repository?
>> Date: Mon, Aug 20, 2012 04:58
>> 
>> 
>> 
>> Hi,
>> 
>> I'm to deploy OpenStack Essex in production environment. According to
>> the official manual, I should either install it manually or use
>> dodai-deploy. After briefly browsing these methods, it seems that both
>> of them are using the packages distributed in official repository
>> (i.e. apt-get install keystone), not building from source like
>> DevStack does.
>> 
>> So my question is, as is said in the title, are these packages
>> production ready? Or should I checkout the stable/essex branch of each
>> project and build it by myself?
>> 
>> Thanks.
>> 
>
>On Mon, Aug 20, 2012 at 08:53:23AM +0200, Ruzicka, Marek wrote:
> Hi,
> 
> Guys around will probably disagree,but I have spent last 5-6weeks
> creating POC using repos is ubuntu, and I have to say it is not
> production rdy yet.
> 
> Versions in repos are about 2months old if I'm not mistaken...too
> old for such fast paced project.
> 
> Marek Ruzicka
> System Engineer (storage)
> T-Systems Slovakia s.r.o.
> 
> Sent from my mobile, please excuse typos.

Hi,

Hmm, I do disagree with this stance.  There are 3 issues being mingled
together, but do have overlap.

1. Is it 'safe' for production.
   - All distributions commit to an assurance level of software they
 ship.  This differs between distributions, and the level of the
 assurance.  However, you can be pretty sure - that any major
 distro will be taking great care of their openstack packages.
   - In relation to Ubuntu, by using the distribution packages you can
 be assured that:
 - Security updates will be included promptly, usually on the day
   the embargo is lifted.
 - Assurance that the software has been tested in given scenarios
   with the dependencies and libraries that are shipped.  Any
   distribution will tell you that a project such as this, the
   core software is only half of the complexity, the dependencies
   carry significant burden.
 - Safe upgrade for security and bug fixes for the release, and
   reasonably easy transition between major versions.  A git
   checkout, doesn't promise safe upgrade.
   - With these factors taken into account, unless significant
 investment into controlling these issues on your own deployment,
 i'd consider it *un-safe* to use anything other than a
 distributions packages.

2. How current are the packages?
   - As mentioned in Marek's email, the packages are about 2 months
 old.  Originally, 12.04 released with Essex Final and some local
 distro patches.  The patches were incorporated upstream, and many
 others contributed fixes.  For this reason, we undertook the
 process of a Stable Release Update.  Due to the level of upstream
 CI, Ubuntu CI and further extended testing, we were able to
 release a snapshot, which seems to have proved to have been
 regression free (!).  This is a testament to the amount of
 pre-release work that went into this update.
   - We are currently preparing the next update, based on Essex
 Stable, which will undergo the same level of care, and should hit
 a mirror near you in a timely manner.
   - For a *stable* release of both upstream, and the distribution
 platform.. I would consider 2 months between updates to be pretty
 good. Some distributions refuse this model for stable updates.

3. Is it 'production ready':
   - Marek seemed to think this was /too/ old.  I'd like specific
 issues to be outlined, regarding the stable tree and our last
 update, which render the distribution packages unsuitable for
 production usage.  If this cannot be done, please re-consider
 this statement.
   - To add to this, Canonical run a two-region hybrid cloud, which is
 purely based on the 12.04/Precise packages. 

I'd also like to take this opportunity to mention the effort that is
going on for Folsom on 12.04.  However, i'll cover this in a separate
mail.

-- 
Kind Regards,

Dave Walker 
Engineering Manager,
Ubuntu Server Infrastructure


signature.asc
Description: Digital 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] [Nova] hostname vs hostIP in live-migration

[Ruzicka, Marek]

Hi Wangpan,

2.
We were dealing with same thing few weeks ago...
Solved it by running another instance of dnsmasq as dns resolver on our 
control-node.
As long as you have small environment as we do, it is pretty simple to keep one 
/etc/hosts up to date.

Regards,

Marek Ruzicka 
System Engineer (Storage)
T-Systems Slovakia s.r.o.
www.t-systems.sk 

-Original Message-
From: openstack-bounces+marek.ruzicka=t-systems...@lists.launchpad.net 
[mailto:openstack-bounces+marek.ruzicka=t-systems...@lists.launchpad.net] On 
Behalf Of Wangpan
Sent: 20. augusta 2012 10:02
To: openstack
Subject: [Openstack] [Nova] hostname vs hostIP in live-migration

Hi all,
I have a doubt about the configuration of live-migration, when we want to use 
the live-migration feature, we show change /etc/hosts on every host, so they 
can establish connection with each other by "hostname", if we don't of forget 
to do this, the live-migration will fail. and also I have look into the source 
code of nova, it uses hostname everywhere instead of hostIP.
So my questions are listed below,
1. Why nova use hostname instead of hostIP ?
2. If there are many compute Nodes, we should change the /etc/hosts on every 
node, and if we want to add one compute Node, we also need to change the 
/etc/hosts of every node, I think this isn't flexible or convenient, is there 
any good ideas? should I configure a DNS server instead of modifing the 
/etc/hosts?
3. I want to modify the source code to change the original implementation by 
add the hostIP to the table 'services' in nova database, so I can get the 
hostIP by querying this table using 'host' as the filter, then I needn't to 
modify the /etc/hosts or add a DNS server to support live-migration. is this a 
feasible plan?

Many Thanks,
Wangpan


___
Mailing list: https://launchpad.net/~openstack
Post to : 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] [Nova] hostname vs hostIP in live-migration

[Wangpan]

Hi all,
I have a doubt about the configuration of live-migration, when we want to use 
the live-migration feature, we show change /etc/hosts on every host, so they 
can establish connection with each other by "hostname", if we don't of forget 
to do this, the live-migration will fail. and also I have look into the source 
code of nova, it uses hostname everywhere instead of hostIP.
So my questions are listed below,
1. Why nova use hostname instead of hostIP ?
2. If there are many compute Nodes, we should change the /etc/hosts on every 
node, and if we want to add one compute Node, we also need to change the 
/etc/hosts of every node, I think this isn't flexible or convenient, is there 
any good ideas? should I configure a DNS server instead of modifing the 
/etc/hosts?
3. I want to modify the source code to change the original implementation by 
add the hostIP to the table 'services' in nova database, so I can get the 
hostIP by querying this table using 'host' as the filter, then I needn't to 
modify the /etc/hosts or add a DNS server to support live-migration. is this a 
feasible plan?

Many Thanks,
Wangpan


___
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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Ji Zhang]

Hi Marek,

Thanks for your reply.

When Folsom comes out, I hope there'll be some sharing experiences on
live-migration.

On Mon, Aug 20, 2012 at 3:46 PM, Ruzicka, Marek
 wrote:
> I would say it depends on your experience with OpenStack.
> You can probably go for folsom-3... Till you find your way around, final 
> release should be out and you can use it in production.
> (It's only a month or so away, and believe me, it will take you that time to 
> install it, get to know it, and test if it suits your production scenario.)
> Just keep in mind, it's kind of development branch.
>
> We are done with our POC on essex. But if are about to proceed to production, 
> it will be done on Folsom once it is out. (there are still lot of things to 
> test till it's out)
> I have no experience with upgrades so far (one of the things to be tested), 
> so I can't tell you how hard it is. I can imagine it really depends on your 
> particular buildup.
>
> Regards,
>
> Marek Ruzicka
> System Engineer (Storage)
> T-Systems Slovakia s.r.o.
> www.t-systems.sk
>
> -Original Message-
> From: Ji Zhang [mailto:zhangj...@gmail.com]
> Sent: 20. augusta 2012 09:18
> To: Ruzicka, Marek
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Is It Safe to Use The OpenStack Packages Distributed 
> in Ubuntu 12.04 Official Repository?
>
> Hi,
>
> So you're suggesting I should install from source. Which branch/tag should I 
> use? branch stable/essex? tag folsom-3?
>
> And also I'm worrying about upgrading and/or migration. Is it expensive to 
> adopt a newer version of openstack?
>
> On Mon, Aug 20, 2012 at 2:53 PM, Ruzicka, Marek  
> wrote:
>> Hi,
>>
>> Guys around will probably disagree,but I have spent last 5-6weeks
>> creating POC using repos is ubuntu, and I have to say it is not production 
>> rdy yet.
>>
>> Versions in repos are about 2months old if I'm not mistaken...too old
>> for such fast paced project.
>>
>> Marek Ruzicka
>> System Engineer (storage)
>> T-Systems Slovakia s.r.o.
>>
>> Sent from my mobile, please excuse typos.
>>
>>
>> - Reply message -
>> From: "Ji Zhang" 
>> To: "openstack@lists.launchpad.net" 
>> Subject: [Openstack] Is It Safe to Use The OpenStack Packages
>> Distributed in Ubuntu 12.04 Official Repository?
>> Date: Mon, Aug 20, 2012 04:58
>>
>>
>>
>> Hi,
>>
>> I'm to deploy OpenStack Essex in production environment. According to
>> the official manual, I should either install it manually or use
>> dodai-deploy. After briefly browsing these methods, it seems that both
>> of them are using the packages distributed in official repository
>> (i.e. apt-get install keystone), not building from source like
>> DevStack does.
>>
>> So my question is, as is said in the title, are these packages
>> production ready? Or should I checkout the stable/essex branch of each
>> project and build it by myself?
>>
>> Thanks.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : 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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Ruzicka, Marek]

I would say it depends on your experience with OpenStack.
You can probably go for folsom-3... Till you find your way around, final 
release should be out and you can use it in production.
(It's only a month or so away, and believe me, it will take you that time to 
install it, get to know it, and test if it suits your production scenario.)
Just keep in mind, it's kind of development branch.

We are done with our POC on essex. But if are about to proceed to production, 
it will be done on Folsom once it is out. (there are still lot of things to 
test till it's out)
I have no experience with upgrades so far (one of the things to be tested), so 
I can't tell you how hard it is. I can imagine it really depends on your 
particular buildup.

Regards,
 
Marek Ruzicka 
System Engineer (Storage)
T-Systems Slovakia s.r.o.
www.t-systems.sk 

-Original Message-
From: Ji Zhang [mailto:zhangj...@gmail.com] 
Sent: 20. augusta 2012 09:18
To: Ruzicka, Marek
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Is It Safe to Use The OpenStack Packages Distributed 
in Ubuntu 12.04 Official Repository?

Hi,

So you're suggesting I should install from source. Which branch/tag should I 
use? branch stable/essex? tag folsom-3?

And also I'm worrying about upgrading and/or migration. Is it expensive to 
adopt a newer version of openstack?

On Mon, Aug 20, 2012 at 2:53 PM, Ruzicka, Marek  
wrote:
> Hi,
>
> Guys around will probably disagree,but I have spent last 5-6weeks 
> creating POC using repos is ubuntu, and I have to say it is not production 
> rdy yet.
>
> Versions in repos are about 2months old if I'm not mistaken...too old 
> for such fast paced project.
>
> Marek Ruzicka
> System Engineer (storage)
> T-Systems Slovakia s.r.o.
>
> Sent from my mobile, please excuse typos.
>
>
> - Reply message -
> From: "Ji Zhang" 
> To: "openstack@lists.launchpad.net" 
> Subject: [Openstack] Is It Safe to Use The OpenStack Packages 
> Distributed in Ubuntu 12.04 Official Repository?
> Date: Mon, Aug 20, 2012 04:58
>
>
>
> Hi,
>
> I'm to deploy OpenStack Essex in production environment. According to 
> the official manual, I should either install it manually or use 
> dodai-deploy. After briefly browsing these methods, it seems that both 
> of them are using the packages distributed in official repository 
> (i.e. apt-get install keystone), not building from source like 
> DevStack does.
>
> So my question is, as is said in the title, are these packages 
> production ready? Or should I checkout the stable/essex branch of each 
> project and build it by myself?
>
> Thanks.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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] Is It Safe to Use The OpenStack Packages Distributed in Ubuntu 12.04 Official Repository?

[Ji Zhang]

Hi,

So you're suggesting I should install from source. Which branch/tag
should I use? branch stable/essex? tag folsom-3?

And also I'm worrying about upgrading and/or migration. Is it
expensive to adopt a newer version of openstack?

On Mon, Aug 20, 2012 at 2:53 PM, Ruzicka, Marek
 wrote:
> Hi,
>
> Guys around will probably disagree,but I have spent last 5-6weeks creating
> POC using repos is ubuntu, and I have to say it is not production rdy yet.
>
> Versions in repos are about 2months old if I'm not mistaken...too old for
> such fast paced project.
>
> Marek Ruzicka
> System Engineer (storage)
> T-Systems Slovakia s.r.o.
>
> Sent from my mobile, please excuse typos.
>
>
> - Reply message -
> From: "Ji Zhang" 
> To: "openstack@lists.launchpad.net" 
> Subject: [Openstack] Is It Safe to Use The OpenStack Packages Distributed in
> Ubuntu 12.04 Official Repository?
> Date: Mon, Aug 20, 2012 04:58
>
>
>
> Hi,
>
> I'm to deploy OpenStack Essex in production environment. According to
> the official manual, I should either install it manually or use
> dodai-deploy. After briefly browsing these methods, it seems that both
> of them are using the packages distributed in official repository
> (i.e. apt-get install keystone), not building from source like
> DevStack does.
>
> So my question is, as is said in the title, are these packages
> production ready? Or should I checkout the stable/essex branch of each
> project and build it by myself?
>
> Thanks.
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : 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