Re: [Openstack] DHCP release

[Robert Collins]

On 23 March 2013 14:53, David Hill  wrote:
> Hello Kevin,
>
> Thanks for replying to my question.   I was asking that question because if 
> we go there: 
> http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-vlan-networking.html
>   and look at the very bottom of the page, it suggests the following:
>
> # release leases immediately on terminate
> force_dhcp_release=true? (did I miss something?)
> # one week lease time
> dhcp_lease_time=604800
> # two week disassociate timeout
> fixed_ip_disassociate_timeout=1209600
>
> I tried that and if you have at some creation/destruction of virtual 
> machines, let's say 2046 in the same week, you'll end up burning the 2046 IPs 
> because they're never disassociated.  At some point, nova-network complains 
> with "no more fixed IP are available".  Changing 
> fixed_ip_disassociate_timeout to something smaller solves this issue.
> Is there any reasons why fixed_ip_disassociate_timeout should be bigger than 
> dhcp_lease_time?
>
> Also, I thought that by destroying a virtual machine, it would 
> release/disassociate the IP from the UUID since it has been destroyed 
> (DELETED).  I've turned on the debugging and with 
> fixed_ip_disassociate_timeout set to 600 seocnds, it disassociate stale IPs 
> after they've been deleted for at least 600 seconds.  Is it a bug in our 
> setup/nova-network or nova-network/manage relies on the periodic task that 
> disassociate stale IPs in order to regain those IPs?
>
> Finaly, wouldn't it be better to simply disassociate a released IP as soon as 
> the VM is deleted?  Since we deleted the VM, why keep it in the database?

When you reuse an IP address you run the risk of other machines that
have the IP cached (e.g. as DNS lookup result, or because they were
configured to use it as a service endpoint) talking to the wrong
machine. The long timeout is to prevent the sort of confusing hard to
debug errors that that happen when machine A is replaced by machine C
on A's IP address.

My 2c: just make your pool larger. Grab 10/8 and have 16M ip's to play with.

-Rob

___
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] DHCP lease not accepted when libvirt_use_virtio_for_bridges=true

[Lorin Hochstein]

On Thu, Mar 21, 2013 at 12:00 PM, Vishvananda Ishaya
wrote:

> Well phooey:
>
>  987 if network_ref['multi_host']:
>  988 _add_dhcp_mangle_rule(dev)
>
> The mangle rule is only added my nova-network in multihost mode.
>
> Can you verify whether or not adding the rule on the compute or network
> node fixes it?
>
> That way we can either remove the check on multi_host or add it in
> plug_vif on the
> compute host.
>
>

I'll check on this and get back to you.

As an aside, note that we're *not* running with the vhost-net kernel module
loaded, and the mangle rule only gets applied if this module is loaded:

https://github.com/openstack/nova/blob/master/nova/network/linux_net.py#L885

884   def _add_dhcp_mangle_rule(dev):
885   if not os.path.exists('/dev/vhost-net'):
886  return

So, either this situation can occur even without vhost-net, or I'm hitting
a different issue.



> BTW:
>
> iptables -D POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM
>>> --checksum-fill
>>>
>>
>
> that should be -A not -D
>
>
D'oh! I'll make sure that's correct when I do the testing.


Lorin




> Vish
>
> On Mar 20, 2013, at 1:43 PM, Lorin Hochstein 
> wrote:
>
>
> On Wed, Mar 20, 2013 at 4:15 PM, Nathanael Burton <
> nathanael.i.bur...@gmail.com> wrote:
>
>> On Wed, Mar 20, 2013 at 3:51 PM, Lorin Hochstein <
>> lo...@nimbisservices.com> wrote:
>>
>>> I'm doing a Folsom deployment with FlatDHCP (not multihost).
>>>
>>> When I try to boot a quantal image, the instance doesn't pick up the
>>> DHCP lease. I've confirmed that dnsmasq is sending out the DHCPOFFER, and I
>>> can see by tcpdump on the compute host that the DHCP packets are making it
>>> to the vnet0 interface.
>>>
>>>
>>> Note that I tried adding this iptables rule as mentioned here <
>>> https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/issues/14>,
>>> but that didn't resolve it.
>>>
>>> iptables -D POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM
>>> --checksum-fill
>>>
>>>
>>>
>>> However, the problem goes away if I change this setting on the compute
>>> hosts in /etc/nova/nova.conf
>>>
>>> libvirt_use_virtio_for_bridges=true
>>>
>>> to:
>>>
>>>libvirt_use_virtio_for_bridges=false
>>>
>>>
>>> Anybody know what would cause this?
>>>
>>>
>>> I'm on Ubuntu 12.04 with the cloud-archive packages, with KVM as the
>>> hypervisor
>>>
>>>
>>> You didn't restart nova-network without killing and restarting dnsmasq,
>> did you?
>>
>> Nate
>>
>>
>>
> Of course not! (Well, maybe...). But just tried again, killing dnsmasq and
> restarting nova-network doesn't seem to help. I'm guessing the issue is
> confined to the compute node, and since I'm not running multihost, I don't
> think I even need to restart nova-network each time I make a virtio-related
> change on the compute node...
>
> Lorin
>
>
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>  ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>


-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
___
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-compute and querying keystone for glance endpoint

[Lorin Hochstein]

On Wed, Mar 20, 2013 at 12:12 AM, Nathanael Burton <
nathanael.i.bur...@gmail.com> wrote:

> On Mar 19, 2013 11:56 PM, "Lorin Hochstein" 
> wrote:
> > OK, so I'm not crazy, that means that I really do need to do something
> like:
> >
> > glance_api_servers=192.168.206.130:9292
> >
> > or (since the default port is used)
> >
> > glance_host=192.168.206.130
> >
> >
> > Lorin
>
> Kinda, if using FLAGS.glance_api_servers you still need to specify the
> port because the code will default to port 80 if not specified [1].  Also
> if your glance server is configured with SSL you would do:
>
> glance_api_servers=https://192.168.206.130:9292
>
> Looking back at the code, your original idea also works.  If you just
> specify FLAGS.glance_host it will build FLAGS.glance_api_servers based on
> your glance_host and the default glance_port [2]. I've always specified the
> glance_api_servers flag since it's the only way to specify SSL.
>
> [1] -
> https://github.com/openstack/nova/blob/stable/folsom/nova/image/glance.py#L84
>
> [2] -
> https://github.com/openstack/nova/blob/stable/folsom/nova/flags.py#L138
>
>
>
I filed an ops bug against nova asking to change the default behavior:
https://bugs.launchpad.net/nova/+bug/1159043

-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
___
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] DHCP release

[David Hill]

Hello Kevin,

Thanks for replying to my question.   I was asking that question because if we 
go there: 
http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-vlan-networking.html
  and look at the very bottom of the page, it suggests the following:

# release leases immediately on terminate
force_dhcp_release=true? (did I miss something?)
# one week lease time
dhcp_lease_time=604800
# two week disassociate timeout
fixed_ip_disassociate_timeout=1209600

I tried that and if you have at some creation/destruction of virtual machines, 
let's say 2046 in the same week, you'll end up burning the 2046 IPs because 
they're never disassociated.  At some point, nova-network complains with "no 
more fixed IP are available".  Changing fixed_ip_disassociate_timeout to 
something smaller solves this issue.
Is there any reasons why fixed_ip_disassociate_timeout should be bigger than 
dhcp_lease_time?

Also, I thought that by destroying a virtual machine, it would 
release/disassociate the IP from the UUID since it has been destroyed 
(DELETED).  I've turned on the debugging and with fixed_ip_disassociate_timeout 
set to 600 seocnds, it disassociate stale IPs after they've been deleted for at 
least 600 seconds.  Is it a bug in our setup/nova-network or 
nova-network/manage relies on the periodic task that disassociate stale IPs in 
order to regain those IPs?   

Finaly, wouldn't it be better to simply disassociate a released IP as soon as 
the VM is deleted?  Since we deleted the VM, why keep it in the database?

Thank you very much,

Dave

From: Kevin Stevens [kevin.stev...@rackspace.com]
Sent: March 22, 2013 18:01
To: David Hill; openstack@lists.launchpad.net
Subject: Re: [Openstack] DHCP release

David,

Maybe I misunderstand your question but I would expect this behavior.  The 
"force_dhcp_release" flag says 'send a DHCP release to the DHCP server'.  This 
doesn't mean that the IP is immediately available for use as it is still 
associated with the instance UUID in the nova database. The 
"fixed_ip_disassociate_timeout" flag disassociates the IP from the relevant 
instance  in the nova.fixed_ips table after the specified time.

Useful link:
http://docs.openstack.org/folsom/openstack-compute/admin/content/list-of-compute-config-options.html

Thanks,
Kevin
Rackspace

From: David Hill mailto:david.h...@ubisoft.com>>
Date: Friday, March 22, 2013 12:59 PM
To: "openstack@lists.launchpad.net" 
mailto:openstack@lists.launchpad.net>>
Subject: [Openstack] DHCP release

Hi guys,

I’m experiencing some kind of weird behaviour with our 
openstack setup here.
Let me explain:
I create an instance that gets an IP: 172.0.0.3
I destroy the instance.
I recreate an instance that will get another IP: 172.0.0.4.

If I wait 600 seconds between each test, 172.0.0.3 will be attributed again 
instead of 172.0.0.4.

Would it be possible that the IP de-allocation relies on the periodic task to 
do some clean up?

I’m asking because actually this doesn’t work:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=1209600

If I do this and stress test my lab, I will eventually run out of IPs!

But this works:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=600

I will eventually start seeing my previously attributed IP address instead of 
running out of IPs.

Am I reading an old document that is outdated?

Thank you very much,

Dave




___
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] DHCP release

[Kevin Stevens]

David,

Maybe I misunderstand your question but I would expect this behavior.  The 
"force_dhcp_release" flag says 'send a DHCP release to the DHCP server'.  This 
doesn't mean that the IP is immediately available for use as it is still 
associated with the instance UUID in the nova database. The 
"fixed_ip_disassociate_timeout" flag disassociates the IP from the relevant 
instance  in the nova.fixed_ips table after the specified time.

Useful link:
http://docs.openstack.org/folsom/openstack-compute/admin/content/list-of-compute-config-options.html

Thanks,
Kevin
Rackspace

From: David Hill mailto:david.h...@ubisoft.com>>
Date: Friday, March 22, 2013 12:59 PM
To: "openstack@lists.launchpad.net" 
mailto:openstack@lists.launchpad.net>>
Subject: [Openstack] DHCP release

Hi guys,

I’m experiencing some kind of weird behaviour with our 
openstack setup here.
Let me explain:
I create an instance that gets an IP: 172.0.0.3
I destroy the instance.
I recreate an instance that will get another IP: 172.0.0.4.

If I wait 600 seconds between each test, 172.0.0.3 will be attributed again 
instead of 172.0.0.4.

Would it be possible that the IP de-allocation relies on the periodic task to 
do some clean up?

I’m asking because actually this doesn’t work:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=1209600

If I do this and stress test my lab, I will eventually run out of IPs!

But this works:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=600

I will eventually start seeing my previously attributed IP address instead of 
running out of IPs.

Am I reading an old document that is outdated?

Thank you very much,

Dave




___
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 Community Weekly Newsletter (Mar 8-22)

[Stefano Maffulli]

   Highlights of the week


 Participate in the first OpenStack User Survey!
 


If you are an OpenStack user or have customers with OpenStack 
deployments, please take 10 minutes to respond to our first User Survey 
or pass it along to your network. Our community has grown at an amazing 
rate in 2.5 years, and it's time to better define our user base and 
requirements, so we can respond and advocate accordingly. TAKE THE 
SURVEY 



 A new agent management approach for Quantum in OpenStack Grizzly
 


In Folsom, Quantum didn't have facilities to schedule its agents between 
cluster nodes, but the Grizzly release brings the support of a new 
component management approach, which addresses this issue.



 Havana Project Technical Leads

Welcome to the new PTLs for OpenStack's future release, Havana:

 * Nova: Russell Bryant
 * Ceilometer: Julien Danjou
 * Keystone: Dolph Matthews
 * Cinder: John Griffith
 * Glance: Mark Washenberger
 * Heat: Steven Dake
 * Horizon: Gabriel Hurley
 * Oslo: Mark McLoughlin
 * Quantum: Marck McClain
 * Swift: John Dickenson

They were elected democratically by their peer developers according to 
the rules of the OpenStack community to lead the next release cycle. 
Congratulations. The new PTLs will join three more people whose election 
is still ongoing, to form the OpenStack Technical Committee.



 *Moving to open development: OpenStack / Crowbar / Chef on SUSE*
 


Crowbar was originally developed by Dell engineers, and is now a 
fully-fledged Open Source project involving close collaboration with 
SUSE and others. There are weekly public meetings 
, a public mailing 
list , a |#crowbar| 
IRC channel , 
public Trello boards 
 and so on. As an 
indication of the project's independent nature, the authoritative 
location for the git repositories has changed from 
https://github.com/dellcloudedge to https://github.com/crowbar, and a 
new homepage is currently under construction.



 OpenStack Miniconf at PyCon Australia 2013
 


PyCon Australia 2013 will be hosting two one-day miniconfs on *Friday 5 
July* before the main conference proceedings kick off on Saturday 6 
July. Miniconfs are events that focus on a specific community that 
relies heavily on Python, and allows practitioners in those communities 
to explore those topics in a much deeper way than the main PyCon 
conference can allow.


The Call For Presenters for the OpenStack Miniconf is open now and 
closes on 15 April, 2013. To submit a presentation, visit the OpenStack 
Miniconf CFP site at 
http://aptira.wufoo.com/forms/pyconau2013-openstack-miniconf-call-for-presenters/



   Tips and Tricks

 * By Anita Kuno : Reviewing an OpenStack Patch
   
 * By Adam Young : Trusts and Role Based
   Access Control for Open Stack
   
 * By Mate Lakat : Virtual Hypervisor: how to
   deploy XenServer inside a XenServer
   
 * By Sébastien Han : Grizzly availability
   zones
   
 * By Yun Mao
   :
   /How to use the ZooKeeper driver for ServiceGroup in OpenStack Nova
   
/
 * By Kashyap Chamarthy : OpenStack ---
   nova image-create, under the hood
   



   Security Advisories

 * OSSA 2013-007] Backend credentials leak in Glance v1 API
   (CVE-2013-1840)
   

 * OSSA 2013-008] Nova DoS by allocating all Fixed IPs (CVE-2013-1838)
   

 * [OSSA 2013-009] Keystone PKI tokens online validation bypasses
   revocation check (CVE-2013-1865)
   



   Upcoming Events

 * OpenStack Hungary Meeting
   
   M

[Openstack] Making networking decision on new OpenStack install

[Willard Dennis]

Hi all,

 

We’ve been playing around with a single-server install of (Folsom) Devstack, 
and have now decided to do the deal and create a multi-node OpenStack 
installation. The installation is going to be for research use for a single 
tenant (the owning research dept) and should not grow that much in physical 
nodes.

 

In any case, being StackNewbs™ we would like to keep it simple and follow a 
good known recipe. Thankfully there’s now a OpenStack Operations Guide we can 
use to get going 😊 However, I see that it uses the older ‘nova-network’ network 
model, and not the new Quantum framework. We do plan to use Folsom as our 
release; is it viable for a few-year lifetime to go with nova-network at this 
point, or should we really consider using Quantum? If Quantum is used, is there 
any instructions available to use that instead of nova-network in the Ops Guide 
type of installation?

 

Thanks for your input...

 

Will___
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] Network layout/planning for HA

[Jonathan Proulx]

On Fri, Mar 22, 2013 at 03:25:56PM -0400, Samuel Winchenbach wrote:

:It looks like 802.3ad is for making parallel, redundant connections.   I
:only have two NICs in the server; I don't think I would want to bind by
:internal and external NICs together would I?

What you want is up to you :)

You could though if you then use VLANs to segregate the internal and
external traffic over the bonded link.  We're not doing this in our
OpenStack but do have older production virtulization systems where
we're using VLANs over bonded NICs.

-Jon

___
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] Network layout/planning for HA

[Samuel Winchenbach]

:o  No, I have never done that before!   Does this seem to be a good
introduction?

http://www.cyberciti.biz/tips/debian-ubuntu-teaming-aggregating-multiple-network-connections.html

It looks like 802.3ad is for making parallel, redundant connections.   I
only have two NICs in the server; I don't think I would want to bind by
internal and external NICs together would I?

Thanks for the reply!   



On Fri, Mar 22, 2013 at 1:00 PM, Mark Lehrer  wrote:

>
>  Quantum seems out because it looks like it requires 3 NICs.  I initially
>>
>
> You can just use VLAN tagging for this.  Personally, unless I have a
> reason not to, I bond 2 nics using 802.3ad and then tag the bond to
> however many VLANs I need.
>
> If you are new to doing this on Linux it will take a good amount of
> playing around to get it right, but it is worth knowing how to do.
>
> Mark
>
___
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] [EHO] Project name change [Savanna]

[Sergey Lukjanov]

Hi everybody,

we have changed our project codename to Savanna (from EHO). Here is our new 
wiki page - https://wiki.openstack.org/wiki/Savanna and new site - 
http://savanna.mirantis.com. 

We decided to do that because of the following reasons:
* we don't want to violate trademarks usage of Hadoop and OpenStack
* we think that Savanna sounds much better than EHO for the english speaking 
audience
* if Savanna will become an integrated OpenStack project, OpenStack Savanna is 
much better than OpenStack Elastic Hadoop on OpenStack
* Savanna is the place where elephants leave :)

Sergey
___
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 and Nova image-list problems (folsom)

[tra26]

Hey,

So glance and nova are returning different results when it comes to images
and snapshots. glance image-list is not returning my private images while
nova image-list returns everyone's private images to everyone. As a result
it seems that horizon won't show any snapshots unless they are public. Is
there some setting I am missing or what?


Thanks,

Trevor


___
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] [EHO] Publishing our first screencast!

[Sergey Lukjanov]

Thanks for a good question!

Yes, sure. Bare metal provisioning will be one of the natural options for EHO 
once it will be fully ready on the OpenStack side. Of course, special images 
with pre-installed Hadoop would be used for it at the first time. The common 
provisioning logic is described in the blogpost you sent.

This feature is in the our internal roadmap and we are waiting for the release 
of bare metal provisioning mechanism in OpenStack to find out how it is ready 
to be used by us out of the box.

Thanks for the notice, we will update our roadmap to cover this feature.

Sergey

On Mar 22, 2013, at 1:10, John van Ommen  wrote:

> Great video.
> 
> I know that OpenStack does baremetal
> (http://www.mirantis.com/blog/bare-metal-provisioning-with-openstack-cloud/);
> 
> Is it possible to do this on bare metal servers instead of VMs?
> 
> John
> 
> On Thu, Mar 21, 2013 at 12:46 PM, Dmitry Mescheryakov
>  wrote:
>> Hello folks,
>> 
>> We've prepared a screencast demonstrating proof-of-concept
>> implementation of Hadoop cluster provisioning:
>> http://www.youtube.com/watch?v=UUt2gqGHcPg
>> 
>> And by the way, it is the first time we're showing our Horizon-based
>> UI in action!
>> 
>> You may find more info at http://eho.mirantis.com
>> 
>> Dmitry
>> 
>> ___
>> 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] DHCP release

[David Hill]

Hi guys,

I'm experiencing some kind of weird behaviour with our 
openstack setup here.
Let me explain:
I create an instance that gets an IP: 172.0.0.3
I destroy the instance.
I recreate an instance that will get another IP: 172.0.0.4.

If I wait 600 seconds between each test, 172.0.0.3 will be attributed again 
instead of 172.0.0.4.

Would it be possible that the IP de-allocation relies on the periodic task to 
do some clean up?

I'm asking because actually this doesn't work:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=1209600

If I do this and stress test my lab, I will eventually run out of IPs!

But this works:
force_dhcp_release=true
dhcp_lease_time=604800
fixed_ip_disassociate_timeout=600

I will eventually start seeing my previously attributed IP address instead of 
running out of IPs.

Am I reading an old document that is outdated?

Thank you very much,

Dave




___
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] Network layout/planning for HA

[Mark Lehrer]

Quantum seems out because it looks like it requires 3 NICs.  I initially


You can just use VLAN tagging for this.  Personally, unless I have a
reason not to, I bond 2 nics using 802.3ad and then tag the bond to
however many VLANs I need.

If you are new to doing this on Linux it will take a good amount of
playing around to get it right, but it is worth knowing how to do.

Mark

___
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] TC candidacy

[Monty Taylor]

I confirm that Vishvananda is eligible to run for a seat on the TC.

On 03/15/2013 05:41 PM, Vishvananda Ishaya wrote:
> Hello all,
> 
> I would like to run for a seat on The Technical Comittee. I have been working 
> on Nova since it was a project as Nasa and I have been heavily involved in 
> openstack since it was founded. I was elected to the precursor to TC (the 
> Project Oversight Committee, later named the Project Policy Board) when it 
> was first created.
> 
> I was also elected as the first PTL for Nova and have been filling that role 
> for the last two years. I am the top contributor to Nova over the lifetime of 
> the project, and the third most frequent contributor over the past 12 months. 
> I helped to create Devstack, Keystone, and Cinder. In addition, I have 
> contributed to Oslo and I am a member of the stable-maintenance team.
> 
> Despite passing on the mantle of Nova PTL, I am still deeply involved with 
> OpenStack and I want to make sure that it continues to be a huge success. As 
> OpenStack grows, one of the most important challenges we face is integration. 
> It is vital that we have technical leaders that are focused cross-project and 
> dedicated to making OpenStack as a whole successful.
> 
> I currently work as the Director of Open Source at Nebula, Inc. Previously I 
> was a principal engineer on the private cloud team at Rackspace, and before 
> that I was a senior developer on the Nebula project at NASA where Nova was 
> created.
> 
> Thanks,
> Vish
> ___
> 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] TC candidacy

[Monty Taylor]

I confirm that Gary is eligible to run for a seat on the TC.

On 03/15/2013 02:13 PM, Gary Kotton wrote:
> Hi,
> 
> I'd like to run for the Technical Committee in the up and coming elections.
> 
> I am a Principle Software Engineer at Red Hat. I have been actively
> developing OpenStack since the Essex release. I am currently a Quantum
> core developer. In addition to this I am also core on the Stable
> Maintenance team. I also have contribute to Nova, OSLO, documentation
> and devstack. In Nova the work was mainly focused on the Quantum
> integrations. My latest contribution was the "VM ensembles", part of
> which was added in Grizzly release and hopefully will be completed in
> the up and coming Havana release. I spend most of my days reviewing,
> testing, debugging, documenting and developing with the goal of making
> OpenStack better. I am thankful to my employer Red Hat to have the
> opportunity and time to work on such and amazing project.
> 
> I have close to 18 years of experience in the industry. Over that course
> of time I have strived to produce quality, usable, robust and optimal
> solutions. I would like to bring all that experience to the table to
> ensure that we have a better product. We are working in a very healthy,
> dynamic and vibrant community. A few things that I would like to improve
> are the following:
> - cross project interaction
> - growth of the community
> - sharing of ideas and information
> 
> In my spare time I run.
> 
> Thanks
> Gary
> 
> 
> 
> 
> ___
> 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] TC Candidacy

[Monty Taylor]

I confirm that Chuck is eligible to run for a seat on the TC.

On 03/16/2013 12:59 PM, Chuck Thier wrote:
> Hello all,
> 
> I would like to run for a seat on the TC.   I am one of the original
> developers of Rackspace Cloud Files which became Openstack Swift, and
> was deeply involved with the creation of Openstack.  I also lead the
> team at Rackspace to create Cloud Block Storage which built off the
> foundation of Openstack Cinder, and during that time contributed
> directly and indirectly to Nova and Cinder.  I have the unique
> experience of not only developing across several Openstack projects, but
> also being responsible for deploying the projects at a very large scale.
>  I have a track record for fighting for reasonable APIs, upgradeability,
> and maintainability across projects.  I have also fought to ensure that
> we have equal and fair representation from all projects in the Openstack
> community. 
> 
> The purpose of the TC is not to "legislate from the bench", but when
> questions and issues are brought to the TC I will continue to support
> these ideals.  I deeply care for Openstack and its future success, so
> please consider me for this position.
> 
> Thanks,
> 
> --
> Chuck Thier
> @creiht
> 
> 
> ___
> 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] TC candidacy

[Monty Taylor]

I confirm that Michael is eligible to run for a seat on the TC.

On 03/15/2013 11:27 AM, Michael Still wrote:
> Hi. I'd like to run for the TC Spring 2013 election. I am a senior
> software engineer at Rackspace in their OpenStack group, and have
> worked in a variety of "cloud devops" roles for the last seven years.
> I think my operations experience gives me an interesting perspective
> into where OpenStack should be going in the next few years.
> 
> My basic platform is the same as for the Nova PTL election [1] -- I
> think we need to get better at closing bugs, and selecting defaults
> which work "out of the box" for OpenStack deployers. We are blessed
> with a very engaged user community, and we need to focus us much as
> possible on giving new users a good experience.
> 
> I am an active Nova and Oslo core reviewer and frequently appear in
> the top ten contributors for Nova in a given month. I am a very active
> code reviewer, especially for Nova. I am also serve on the OpenStack
> Vulnerability Management Team. I strongly believe in the future of
> OpenStack and want to be part of that success in any way I can. For
> the last two years my non-OpenStack open source contributions have
> mainly been as Director for linux.conf.au 2013, which was the largest
> OpenStack event to be run in Australia so far.
> 
> Thanks,
> Michael
> 
> 1: http://lists.openstack.org/pipermail/openstack-dev/2013-March/006417.html
> 
> ___
> 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 grizzly rc1 packages availability for Debian

[Emilien Macchi]

Hi,

You can find more informations about the packages here :

http://qa.debian.org/developer.php?login=openstack-de...@lists.alioth.debian.org

And join us on #debian-openstack (OFTC) !


Regards,

Emilien Macchi

# OpenStack Engineer
// eNovance Inc.  http://enovance.com
// ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris

On 03/22/2013 02:03 PM, Mohammed Amine SAYA wrote:
> Hi All,
> 
> I ran into quantum dhcp issue described in bug 1135948 and I also learned
> that it has been fixed in quantum grizzly-rc1. Does somebody know something
> about grizzly-rc1 package availability for DEBIAN ?
> 
> Thanks for your help,
> Amine.
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 



signature.asc
Description: OpenPGP 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] Is it possible to change VM NIC into a new subnet without rebuild?

[Sylvain Bauza]

Hi Johanna,

Le 22/03/2013 14:36, Heinonen, Johanna (NSN - FI/Espoo) a écrit :

Hi,
We want  somehow to add a new interface to a running VM. To modify an 
existing interface (by assigning it to a new subnet) could be also an 
alternative.



Quantum port-update  --fixed_ip ip_address=x.x.x.x
This command was executed successfully but did not have any effect.



You will have to restart quantum-dhcp-agent and reask for a DHCP lease 
on the VM.


-Sylvain
___
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] TC election open

[Monty Taylor]

If you are an ATC, you should by this point have received a link that
will let you vote in the OpenStack TC election. You should vote.

If you read it, you will note that it says February 28 is the end date.
That is an error - March 28 is the end date.

___
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] TC candidacy

[Monty Taylor]

I confirm that Eric is eligible to run for a seat on the TC.

On 03/18/2013 03:23 PM, Eric Windisch wrote:
> Hello,
> 
> I'd like to run for a seat on the Technical Committee. I am a Principal 
> Engineer at Cloudscaling, but I am running as an individual.
> 
> For over two years, beginning with Bexar, I have been working to bring 
> working OpenStack solutions to customers. My first code contributions landed 
> in Cactus, but my contributions have not been limited to code alone. I 
> propose and drive summit and mailing list discussions, contribute to those 
> discussions led by others, have begun contributing to packaging efforts, and 
> soon intend to land documentation changes.
> 
> The code I do write and review tends to be in Oslo. Working with Oslo, and 
> with OpenStack deployments, I have the perspective to work across projects.
> 
> Before my involvement with OpenStack, in my former role as the owner and 
> technical director of a VPS hosting company, I was already building open 
> source cloud infrastructure as early as 2007.  For years preceding the 
> existence of OpenStack, I've worked on many of the technical problems and 
> challenges facing a cloud, not only those related to virtualization, 
> networking, and storage, but also billing, metering, and user interfaces.
> 
> The number of companies and contributors involved in OpenStack is exploding. 
> Each conference has been shockingly larger than the last. We have new 
> projects being added in each 6-month release. These are problems that the TC 
> must be prepared to deal with. We need technical leadership that understands 
> the problems of these projects, can help them succeed, and especially for 
> those individually elected seats -- can bring them to together.
> 
> I am deeply committed to the success of OpenStack and to open source cloud. I 
> thank you for your consideration and ask that you please vote for me. 
> 
> Regards,
> Eric Windisch
> 
> 
> 
> ___
> 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] TC candidacy

[Monty Taylor]

I confirm that Chris is eligible to run for a seat on the TC.

On 03/18/2013 06:11 PM, Chris Behrens wrote:
> 
> Hi all,
> 
> I'd like to announce my candidacy for a seat on the OpenStack
> Technical Committee.
> 
> - General background -
> 
> I have over 15 years of experience designing and building distributed
> systems.  I am currently a Senior Software Developer at Rackspace,
> where I have been for a 2 and a half years now.  Most of my time
> at Rackspace has been spent working on OpenStack as both a developer and
> a technical leader.  My first week at Rackspace was spent at the very first
> OpenStack Design Summit in Austin where the project was announced.
> 
> Prior to working at Rackspace, I held various roles over 14 years
> at Concentric Network Corporation/XO Communications including Senior
> Software Architect and eventually Director of Engineering.  My main
> focus there was on an award winning web/email hosting platform which
> we'd built to be extremely scalable and fault tolerant.  While my
> name is not on this patent, I was heavily involved with the development
> and design that led to US6611861.
> 
> - Why am I interested? -
> 
> I have strong feelings for OpenStack and I want to help take it to
> the next level.  I have a lot of technical knowledge and experience
> building scalable distributed systems.
> 
> During most of my past experience, I haven't had the luxury of having
> access to a lot extremely fast hardware, so it's been important to
> make software as performant as possible.  I've also had to put lots of
> effort into having 0 downtime, meaning code can be updated seamlessly
> without dropping clients.  I've also been one to lead host and software
> security efforts so I have a lot of strong feelings in this area.
> 
> I am extremely interested in using this experience to make OpenStack
> perform well, be secure, be more easily pluggable, and easy to use!
> 
> - OpenStack contributions -
> 
> As I mentioned above, I was at the very first design summit, so
> I've been involved with the project from the beginning.  I started
> the initial work for nova-scheduler shortly after the project was
> opened.  I also implemented the RPC support for kombu, making sure
> to properly support reconnecting and so forth which didn't work
> quite so well with the carrot code.  I've contributed a number of
> improvements designed to make nova-api more performant.  I've worked on
> the filter scheduler as well as designing and implementing the
> first version of the Zones replacement that we named 'Cells'.
> 
> I'm currently looking forward to restructuring our use of DB API to better
> support upgrades w/ schema changes as well as committing an alternative
> DB backend implementation for mysql that significantly reduces how long
> we block on DB API calls compared to sqlalchemy.
> 
> - Summary -
> 
> I feel my years of experience contributing to and leading large scale
> technical projects along with my knowledge of the OpenStack projects
> will provide a good foundation for technical leadership.
> 
> Thanks,
> 
> - Chris
> 
> 
> ___
> 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] TC candidacy

[Monty Taylor]

I confirm that Carl is eligible to run for a seat on the TC.

On 03/15/2013 07:08 PM, Carl Perry wrote:
> Greetings -
> 
> I would like to run for a TC seat as well. My platform is a focus on
> deployment and operations for OpenStack. I'm not going to mince words:
> deploying OpenStack is hard. Maintaining it is even harder. I don't
> think it needs to be this way. I spent two years designing and deploying
> a cloud based on OpenStack and it really seemed much harder to do than
> it should have been, especially when you factor in configuration
> management tools.
> 
> I would like to promote a more operational approach to the decisions
> made inside the OpenStack community. Some of it is easy, some of it is
> hard. I don't expect things to change overnight, but I do feel that a
> course correction is needed, that it's going to need to come from a
> whole project approach as well as code contribution, and that now is the
> time to make it.
> 
> As I said, I spent the last two years as an implementor of OpenStack
> with the DreamCompute project at DreamHost and have now moved on to a
> new position as a solutions architect at Midokura. These positions have
> given (and continue to give) me a customer perspective of what it takes
> to deploy, maintain, and upgrade OpenStack in production. While my
> company supports me and my desire to run for the TC, I'm running
> independent of my company in order to keep a vendor neutral approach.
> 
> Thanks for your time!
>   -Carl
> 
> ___
> 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] TC candidacy

[Monty Taylor]

I confirm that Thierry is eligible to run for a seat on the TC.

On 03/15/2013 11:32 AM, Thierry Carrez wrote:
> Hi everyone,
> 
> I'd like to run for reelection to one of the Technical Committee
> directly-elected seats.
> 
> For those who don't know me, I've been handling release management
> duties for OpenStack since November 2010, a work currently sponsored by
> the OpenStack Foundation. My involvement is mostly around project
> coordination, keeping a global view and trying to anticipate issues as
> our development community grows even larger. I'm also heading the
> Vulnerability Management team, which handles incoming security issues
> reports. On the development side, I authored the rootwrap framework
> which is being used by a few of our projects, and whenever I find some
> free time, I'm working on improving it.
> 
> I've been regularly elected by our community to the Project Policy Board
> and Technical Committee directly-elected seats for the last two years. I
> was heavily involved in the transition to our new governance, authored
> the Technical Committee charter, and have been chosen to chair it for
> the past 6 months.
> 
> I think it's important that the Technical Committee contains
> representation from the horizontal functions within the project (Docs,
> QA, Infrastructure, Vulnerability management, Release management...),
> since each project is already represented by the seats granted for all PTLs.
> 
> Over the last 30 months we grew from 2 projects to 10 projects, and I'm
> proud to be part of this community which successfully managed to handle
> growth and adoption while preserving our ideals of open design and open
> development.
> 
> The challenges ahead of us include accommodating further growth, resist
> fragmentation, and maintaining efficiency and coherence as we grow well
> past Dunbar's number. I hope that you place me in a position where I can
> help us through those challenges.
> 
> 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

[Openstack] Network layout/planning for HA

[Samuel Winchenbach]

Hi All,

I am trying (keyword trying) to get a highly available cluster going.
 Currently I have most of the services needed (mysql, rabbitmq, glance,
keystone, etc.) configured as resources in pacemaker and that works quite
nicely.   Now I need to figure out networking.

I have 2 servers with 2 NICs, one NIC is a public interface and the other
is on an internal network.  This is likely to increase to three servers in
the near future to help with quorum/split brain issues.  I plan on these
servers being a combination control/networking hosts.  On the internal
network I have several compute nodes.

What are some of my networking options?

Quantum seems out because it looks like it requires 3 NICs.  I initially
tried adding my public IP to external bridge interface hoping I could get
away with 2 NICs but I could't get it to work.  If someone could explain
why quantum requires 3 interfaces that would be great.

That leaves nova-network.   Seeing my compute nodes are behind the
control/networking nodes does that mean multi_host is out of the question?
  If so that really only leaves creating a VIP in pacemaker and moving it
around with nova-network with pacemaker correct?

Thanks all for reading and any suggestions you may have!
Sam
___
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] Is it possible to change VM NIC into a new subnet without rebuild?

[Heinonen, Johanna (NSN - FI/Espoo)]

Hi,

We want  somehow to add a new interface to a running VM. To modify an existing 
interface (by assigning it to a new subnet) could be also an alternative.
We tried the following:

Quantum port-update  --device_id 
This worked but required nova rebuild command.

Quantum port-update  --fixed_ip ip_address=x.x.x.x
This command was executed successfully but did not have any effect.


Do you have any suggestions what we could try next or is this currently 
something that is not possible to do?

BR
Johanna


___
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 : working without ephemeral disk, only persistance cinder "bootable" volume.

[Benoit ML]

Hello,

I'm working about an openstack cloud architecture. Well I'd like to
work only with persistance volume.

My hypervisor (compute node) will only have a small sized system disk
(flash cache, usb key, something like this).
And I will have a NetApp SAN for iSCSI, controlled by cinder.

I presume i will have about 20-40 nova profiles.

Well so have you got any exemple of working with  bootable volume ?
What will be the best methode ?
How to easy  handle and create bootable volume from multiple différent
 OS ? And in OpenStack Folsom  the cinder "copy_id_image_to_volume"
doesnt work ...

Thank you in advance !

Regards,
--
Benoit

___
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 grizzly rc1 packages availability for Debian

[Mohammed Amine SAYA]

Hi All,

I ran into quantum dhcp issue described in bug 1135948 and I also learned
that it has been fixed in quantum grizzly-rc1. Does somebody know something
about grizzly-rc1 package availability for DEBIAN ?

Thanks for your help,
Amine.
___
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] A question on Unique ID for instance in Compute v2.0 api

[Bob Ball]

In terms of XenServer, I don't think the UUID typically presented via the bios.

You can get it either by reading /sys/hypervisor/uuid or by using xenstore-read 
(e.g. xenstore-read domid followed by xenstore-read /local/domain//vm)

Thanks,

Bob

From: openstack-bounces+bob.ball=citrix@lists.launchpad.net 
[mailto:openstack-bounces+bob.ball=citrix@lists.launchpad.net] On Behalf Of 
Zhiqiang Zhao
Sent: 22 March 2013 07:30
To: openstack@lists.launchpad.net
Subject: [Openstack] A question on Unique ID for instance in Compute v2.0 api

Hi Experts,

Is the id the same as uuid for vms? I've checked it when I use qume to lauch 
vms.
Dmidecode in vm console:
[root@10-0-0-6 ~]# ./dmidecode -t system
# dmidecode 2.10
SMBIOS 2.4 present.

System Information
Manufacturer: OpenStack Foundation
Product Name: OpenStack Nova
Version: 2013.1
Serial Number: 42139d49-16d1-0942-ae83-3c529bb30435
UUID: F1998E0A-B45A-4149-A06A-F8975FEFDB68
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified

openstack json response:
{"server": {"status": "ACTIVE", "updated": "2013-03-11T01:59:03Z", "hostId": 
"ee8502390822a52801706dcdbe42369c5a12f3f2debbff60726a4ce7", 
"OS-EXT-SRV-ATTR:host": "crdc-210-5-2-control.cisco.com", "addresses": 
{"private": [{"version": 4, "addr": "10.0.0.6", "OS-EXT-IPS:type": "fixed"}]}, 
"links": [{"href": 
"http://10.74.125.74:8774/v2/ec38725672344e0ba756bc007a420b66/servers/f1998e0a-b45a-4149-a06a-f8975fefdb68";,
 "rel": "self"}, {"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/servers/f1998e0a-b45a-4149-a06a-f8975fefdb68";,
 "rel": "bookmark"}], "key_name": null, "image": {"id": 
"c946b09d-ad2f-4c06-873b-bcc08000824d", "links": [{"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/images/c946b09d-ad2f-4c06-873b-bcc08000824d";,
 "rel": "bookmark"}]}, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": 
"active", "OS-EXT-SRV-ATTR:instance_name": "instance-0010", 
"OS-EXT-SRV-ATTR:hypervisor_hostname": "crdc-210-5-2-control.cisco.com", 
"flavor": {"id": "bcbdb244-e98a-4f11-954c-fb0fcf2cae6e", "links": [{"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/flavors/bcbdb244-e98a-4f11-954c-fb0fcf2cae6e";,
 "rel": "bookmark"}]}, "id": "f1998e0a-b45a-4149-a06a-f8975fefdb68", 
"security_groups": [{"name": "default"}], "OS-EXT-AZ:availability_zone": 
"nova", "user_id": "cd62dcd084ae4078b9e5cedaac6d8dcd", "name": "test2", 
"created": "2013-03-11T01:58:54Z", "tenant_id": 
"ec38725672344e0ba756bc007a420b66", "OS-DCF:diskConfig": "MANUAL", 
"accessIPv4": "", "accessIPv6": "", "progress": 0, "OS-EXT-STS:power_state": 1, 
"config_drive": "", "metadata": {}}}

You can see UUID is consistent with ID.
My question is: If I use ESXi or XEN as hypervior, is it always correct by this 
way? Currently I'm just using QUME to lauch vms.

Best Regards!
Henry

___
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] [DevStack] DevStackInstallation with XEN

[HuYanrui]

Hi, Bob,
Thanks for you feedback. But I still can not finish the installation after 
viewed the material you provided.
That README.md is same with the one in my previous mail.
the install-devstack-xen.sh seems new one so what I do today is based on this.
My Xenserver PC has two NIC, one is 10.8.x.x, the other is 10.11.x.x (but did 
not config this IP at xenserver side, set it in shell)
After install-devstack-xen.sh run, the devstackosdomu will display "Bad archive 
mirror" when "Choose a mirror of the Ubuntu archive "
What's the probably reason for this?

And please also confirm one thing: After all these was setup, can I use 
openstack webui to manage the VMs imported inside Xenserver?

Following is the shell I used for reference:

#!/bin/bash
#
# This script installs a DevStack DomU VM on
# the specified XenServer.
set -e

function syntax {
echo "Syntax: $0   "
echo "Environment variables \$PrivID, \$Server and"\
" \$XenServerPassword can be used as an alternative"
exit 1
}

function create_template {
cat > $1 < $tmpdir/key.pub

ssh_options="-o BatchMode=yes -o StrictHostKeyChecking=no "
ssh_options+="-o UserKnownHostsFile=/dev/null -i $PrivID"

# Now we have our variables set up, ensure we don't mis-type them
set -u

# Tolerate this ssh failing - we might need to copy the key across
set +e
ssh -o LogLevel=quiet $ssh_options root@$Server /bin/true >/dev/null 2>&1
if [ $? != 0 ] ; then
set -e
echo "Please supply password for ssh-copy-id.  " \
"This should be the last time the password is needed:"
ssh-copy-id -i $tmpdir/key.pub root@$Server
fi
set -e


GENERATED_LOCALRC=$tmpdir\localrc

# Generate localrc
cat $TEMPLATE_LOCALRC |
sed -e "s,%XenServerVmVlan%,$XenServerVmVlan,g;
s,%XenServerPassword%,$XenServerPassword,g;
" > $GENERATED_LOCALRC

LocalrcAppend=${LocalrcAppend-"localrc.append"}
[ -e "${LocalrcAppend}" ] && ( cat "$LocalrcAppend" >> $GENERATED_LOCALRC ) || \
echo "$LocalrcAppend was not found, not appending to localrc"

set -x

# The parmaters expected are:
# $Server - XenServer host for compute DomU
# $XenServerVmVlan - Vlan ID
# $XenServerPassword - Password for your XenServer

# $MirrorHttpHostname (default:archive.ubuntu.com)- Ubuntu mirror to use
# $MirrorHttpDirectory (default: /ubuntu) - directory within the http mirror
# $MirrorHttpProxy (default: ) - http proxy to use
# $DevStackURL (optional) - URL of the devstack zip file
# $CleanTemplates (default:false) - If true, clean the templates

MirrorHttpHostname=${MirrorHttpHostname-"archive.ubuntu.com"}
MirrorHttpDirectory=${MirrorHttpDirectory-"/ubuntu"}
MirrorHttpProxy=${MirrorHttpProxy-""}
DevStackURL=${DevStackURL-"https://github.com/openstack-dev/devstack/zipball/master"}
CleanTemplates="${CleanTemplates-false}"
DhcpTimeout=120

#
# Add the clean templates setting
# and correct the IP address for dom0
#
XenApiIP=`ssh $ssh_options root@$Server "ifconfig xenbr0 | grep \"inet addr\" | 
cut -d \":\" -f2 | sed \"s/ .*//\""`
cat <> $GENERATED_LOCALRC
CLEAN_TEMPLATES=$CleanTemplates
XENAPI_CONNECTION_URL="http://$XenApiIP";
VNCSERVER_PROXYCLIENT_ADDRESS=$XenApiIP
EOF

#
# Show the content on the localrc file
#

set +x
echo "Content of localrc file:"
cat $GENERATED_LOCALRC
echo "** end of localrc file **"

#
# Run the next steps on the XenServer host
#

#
# Clean directory, create directory and
# copy what we need to the XenServer
#
SCRIPT_TMP_DIR=/tmp/jenkins_test

cat > $tmpdir/install_devstack.sh <--)
# so the output is in a "devstack" directory
unzip -oq $SCRIPT_TMP_DIR/devstack.zip -d $SCRIPT_TMP_DIR/tmpunzip
mv $SCRIPT_TMP_DIR/tmpunzip/* $SCRIPT_TMP_DIR/devstack
rm -rf $SCRIPT_TMP_DIR/tmpunzip

preseedcfg=$SCRIPT_TMP_DIR/devstack/tools/xen/devstackubuntupreseed.cfg
sed -ie "s,\(d-i mirror/http/hostname string\).*,\1 ${MirrorHttpHostname},g" 
\$preseedcfg
sed -ie "s,\(d-i mirror/http/proxy string\).*,\1 ${MirrorHttpProxy},g" 
\$preseedcfg
sed -ie "s,\(d-i mirror/http/directory string\).*,\1 ${MirrorHttpDirectory},g" 
\$preseedcfg
# Additional DHCP timeout
sed -ie "s,#\(d-i netcfg/dhcp_timeout string\).*,\1 ${DhcpTimeout},g" 
\$preseedcfg

cp /tmp/localrc $SCRIPT_TMP_DIR/devstack/localrc

pushd $SCRIPT_TMP_DIR/devstack/tools/xen/
./install_os_domU.sh
popd
EOF

chmod +x $tmpdir/install_devstack.sh
echo
echo "*** Content of install_devstack.sh ***"
cat $tmpdir/install_devstack.sh
echo "*** End of install_devstack.sh ***"

set -x

scp $ssh_options $PrivID "root@$Server:~/.ssh/id_rsa"
scp $ssh_options $tmpdir/key.pub "root@$Server:~/.ssh/id_rsa.pub"
scp $ssh_options "$GENERATED_LOCALRC" "root@$Server:/tmp/localrc"
scp $ssh_options "$tmpdir/install_devstack.sh" 
"root@$Server:/tmp/install_devstack.sh"
ssh $ssh_options root@$Server "chmod +x /tmp/install_devstack.sh && 
/tmp/install_devstack.sh" \
" | tee $SCRIPT_TMP_DIR/install_devstack.log"
  - Original Message - 
  From: Bob Ball 
  To: 'HuYanrui' ; openstack@lists.launchpad.net 
  Sent: Th

[Openstack] [Keystone] OpenStack Identity Grizzly RC1 available

[Thierry Carrez]

Hello everyone,

Last but not least, OpenStack Identity (codenamed Keystone) just
published its first Grizzly release candidate. It is available for
download at:

https://launchpad.net/keystone/grizzly/grizzly-rc1

Congrats to the Keystone crew.

Unless release-critical issues are found that warrant a release
candidate respin, this RC1 will be formally released as Keystone 2013.1
final version on April 4. You are therefore strongly encouraged to test
and validate this tarball.

Alternatively, you can directly test the milestone-proposed branch at:
https://github.com/openstack/keystone/tree/milestone-proposed

If you find an issue that could be considered release-critical, please
file it at:

https://bugs.launchpad.net/keystone/+filebug

and tag it *grizzly-rc-potential* to bring it to the release crew's
attention.

The Keystone "master" branch is now open for Havana development, and
feature freeze restrictions no longer apply.

Regards,

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
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] A question on Unique ID for instance in Compute v2.0 api

[Zhiqiang Zhao]

Hi Experts,


Is the id the same as uuid for vms? I've checked it when I use qume to lauch 
vms. 
Dmidecode in vm console:
[root@10-0-0-6 ~]# ./dmidecode -t system
# dmidecode 2.10
SMBIOS 2.4 present.


System Information
Manufacturer: OpenStack Foundation
Product Name: OpenStack Nova
Version: 2013.1
Serial Number: 42139d49-16d1-0942-ae83-3c529bb30435
UUID: F1998E0A-B45A-4149-A06A-F8975FEFDB68
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified


openstack json response:
{"server": {"status": "ACTIVE", "updated": "2013-03-11T01:59:03Z", "hostId": 
"ee8502390822a52801706dcdbe42369c5a12f3f2debbff60726a4ce7", 
"OS-EXT-SRV-ATTR:host": "crdc-210-5-2-control.cisco.com", "addresses": 
{"private": [{"version": 4, "addr": "10.0.0.6", "OS-EXT-IPS:type": "fixed"}]}, 
"links": [{"href": 
"http://10.74.125.74:8774/v2/ec38725672344e0ba756bc007a420b66/servers/f1998e0a-b45a-4149-a06a-f8975fefdb68";,
 "rel": "self"}, {"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/servers/f1998e0a-b45a-4149-a06a-f8975fefdb68";,
 "rel": "bookmark"}], "key_name": null, "image": {"id": 
"c946b09d-ad2f-4c06-873b-bcc08000824d", "links": [{"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/images/c946b09d-ad2f-4c06-873b-bcc08000824d";,
 "rel": "bookmark"}]}, "OS-EXT-STS:task_state": null, "OS-EXT-STS:vm_state": 
"active", "OS-EXT-SRV-ATTR:instance_name": "instance-0010", 
"OS-EXT-SRV-ATTR:hypervisor_hostname": "crdc-210-5-2-control.cisco.com", 
"flavor": {"id": "bcbdb244-e98a-4f11-954c-fb0fcf2cae6e", "links": [{"href": 
"http://10.74.125.74:8774/ec38725672344e0ba756bc007a420b66/flavors/bcbdb244-e98a-4f11-954c-fb0fcf2cae6e";,
 "rel": "bookmark"}]}, "id": "f1998e0a-b45a-4149-a06a-f8975fefdb68", 
"security_groups": [{"name": "default"}], "OS-EXT-AZ:availability_zone": 
"nova", "user_id": "cd62dcd084ae4078b9e5cedaac6d8dcd", "name": "test2", 
"created": "2013-03-11T01:58:54Z", "tenant_id": 
"ec38725672344e0ba756bc007a420b66", "OS-DCF:diskConfig": "MANUAL", 
"accessIPv4": "", "accessIPv6": "", "progress": 0, "OS-EXT-STS:power_state": 1, 
"config_drive": "", "metadata": {}}}


You can see UUID is consistent with ID. 
My question is: If I use ESXi or XEN as hypervior, is it always correct by this 
way? Currently I'm just using QUME to lauch vms.


Best Regards!
Henry___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp