Re: [Openstack] What is the typical way to deploy OpenStack Compute with ESXi

[Sean Chen]

Both physical machine and VM work. It's preferred to install nova compute
on a VM hosted on the ESXi that nova compute manages.

-- 
Sean
___
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] How to create vm instance to specific compute node?

[Anne Gentle]

Great to know, Phil!

We did add to the docs to explain that you couldn't choose a host any more:

http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html
and then added this page to let people know how to choose a zone

http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-zone-to-boot-instances-on.html

This doc bug requests the additional information about the policy
enforcement so we can update the doc.
https://bugs.launchpad.net/openstack-manuals/+bug/1096168

Thanks,
Anne



On Thu, Jan 3, 2013 at 7:03 AM, Day, Phil  wrote:

> > Note this is an admin-only ability by default and can oversubscribe the
> compute node the instance goes on.
>
> It is now controlled by a policy (create:forced_host) - so if you want to
> extend it to other users you can, for example, set up the policy file to
> control this via a Keystone role
>
> Phil
>
> -Original Message-
> From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:
> openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of Jay
> Pipes
> Sent: 27 December 2012 22:39
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] How to create vm instance to specific compute
> node?
>
> No.
>
> Use nova boot --availability_zone=nova:hostname where nova: is your
> availability zone and hostname is the hostname of the compute node you wish
> to put the instance on.
>
> Note this is an admin-only ability by default and can oversubscribe the
> compute node the instance goes on.
>
> Best,
> -jay
>
> On 12/27/2012 02:45 PM, Rick Jones wrote:
> > Does the convention of adding --onhost--computenodename to the instanc
> > name being created still work?
> >
> > rick jones
> >
> > ___
> > 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

[Openstack] [Cinder] cinder-agent

[Akira Yoshiyama]

Hi all,

JOSUG (Japanese OpenStack User Group) had a regular hackathon in Tokyo
last month.
We discussed about Quantum and Cinder, and got an idea about 'cinder-agent'.

Now Cinder has many server-side drivers for volume service and nova-compute has
client-side drivers to use it. If other software like CloudStack,
OpenNebula and so on use
Cinder, they will have to implement their own client-side drivers for
Cinder. But they don't
have to do it for Quantum because it has a client service
'quantum-agent' and others.

I think Cinder should have its own client service 'cinder-agent'.
There are many benefits:

* We can remove volume-related drivers (server/client side) from Nova perfectly.
  * Nova can be used with newer/older Cinder.
  * Both-side volume drivers can be added or updated with one patch for Cinder.
* Attaching/detaching volume API can be simple because Cinder can use
RPC to do them.
  For example:
Attaching volume request:
  POST /v2/{tenant_id}/servers/{server_id}/os-volume_attachments_with_agent
  {'volume'] '{volume_id}', 'host': '{host_name}'}
Response body:
  {'volume': '{volume_id}', 'host': '{host_name}', 'path': '{device_path}'}
# {host_name}: the host name with nova-compute and cinder-agent
* Of course, any software can use Cinder without client-side volume drivers.

Any comments?

Regards,
   Akira YOSHIYAMA 

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] swift -- object layout on storage

[John Dickinson]

It's pretty simple. Swift uses the underlying filesystem to store the data on 
disk, and so you can use normal FS tools to find and inspect your data.

For the object server, the "magic" happens here: 
https://github.com/openstack/swift/blob/master/swift/obj/server.py#L117

The end result is that the data is stored here:

/path/to/mount/points/device/objects/partition/hash_suffix/hash/

That directory is the object. Inside the directory, there is normally just one 
file (named .data). The object's data is stored in the file, and the 
object's metadata is stored in the xattrs of the file.

In some cases (mostly around failure handling), there may be more than one file 
in that directory, but for the general case, all the .data files are sorted (by 
filename) and the last is chosen (ie the most recent). As I said, there is 
normally just the one file in there.

If you delete the object, the .data file is deleted and a .ts ("ts" 
for "tombstone") file is created as a zero-byte file. This is a delete marker 
that will be eventually reaped, but it exists to ensure that the delete 
properly propagates to all replicas in the cluster.

--John

 

On Jan 4, 2013, at 10:14 AM, "Snider, Tim"  wrote:

> I’d like to understand more on how Swift lays out objects on the underlaying 
> storage. I can’t seem to find out  much about this in the openstack / swift 
> documentation itself or in associated web searchs.
> Thanks for pointers / links.
> Tim
> ___
> 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

[Openstack] swift -- object layout on storage

[Snider, Tim]

I'd like to understand more on how Swift lays out objects on the underlaying 
storage. I can't seem to find out  much about this in the openstack / swift 
documentation itself or in associated web searchs.
Thanks for pointers / links.
Tim
___
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 - Switch Network mode

[Vishvananda Ishaya]

I don't think you can keep the same ip addresses. You will have to manually 
stop vms and recreate themn in libvirt with new ip addresses, while making sure 
to manually create all of the db tables for networks properly.

Your best bet might be to snapshot all of your vms into glance, delete and 
reinstall nova in vlan mode, and relaunch the vms from the snapshots.


Alternatively, you could try installing a vlan version somewhere new, running a 
new vm for each vm in your old system, then manually stopping those vms and 
overwriting their disk files with your old disk files and restarting. The guest 
os might complain about the change in mac address though, so you may have to 
vnc in and manually fix some networking issues in your guests.

Vish


On Jan 4, 2013, at 3:32 AM, Bruno Parreira  wrote:

> Even being extremely difficult what would have to be done? we can stop the 
> VMs if that helps.
> 
> Bruno
> 
> Enviado do meu iPad
> 
> No dia 03/01/2013, às 21:18, Vishvananda Ishaya  
> escreveu:
> 
>> This will be extremely difficult. I wouldn't recommend it.  It would 
>> probably be easier to make a manual cloudpipe instance instead of having 
>> nova manage it. You will just have to do some tweaking of the nwfilter rules 
>> of the vm. An even easier solution would be to just make a bastion vm that 
>> the collaborators can ssh through.
>> 
>> Vish
>> 
>> On Jan 3, 2013, at 12:05 PM, bruno sendas  wrote:
>> 
>>> Hi,
>>> 
>>> We have OpenStack Folsom deployed in one computer where there are several 
>>> VM's running and we want to instantiate cloudpipe to  provide access to 
>>> external collaborators. 
>>> 
>>> The problem is that the network was deployed using Flat DHCP mode and now 
>>> we have to change it to VLAN mode, is it possible to change the networking 
>>> mode without having to shutdown the VM's ? Can anybody give the main steps 
>>> or tips to change the networking mode in the least disrupting way?
>>> 
>>> Kind regards,
>>> Bruno Sendas ___
>>> 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] OpenStack Community Weekly Newsletter (Dec 28 – Jan 4)

[Stefano Maffulli]

   Highlights of the week


 Save the Date – OpenStack Summit Spring 2013
 


*It’s official – the Spring 2013 OpenStack Summit 
 will be held in 
Portland, April 15-18, at the Oregon Convention Center. *


We’re expecting 2000 OpenStack users, prospective users, ecosystem 
members and developers to attend the Spring Summit. As usual, we’ll have 
a variety of content and tracks, ranging from compelling user stories 
and technical deep dives to the business case for OpenStack and hands-on 
workshops.


If you’d like to submit a presentation, panel or workshop, the *call for 
speakers 
is now 
open* and will close February 15.


The call for sponsorships will open January 14*. *Event registration and 
discount hotel rates will be available the week of January 14, so stay 
tuned and check back for updates .



 OpenStack Board of Directors Talks: Episode 3 with Randy Bias,
 Co-Founder & CTO at Cloudscaling
 

Rafael Knuth chats with Randy Bias about Cloudscaling, OpenStack, cloud 
technology, API compatibility, enterprise adoption of cloud 
technologies, Dell and more.



   Tips and tricks

 * By Hui Cheng : How To Build A Small Hadoop
   Cluser In Openstack Using Hadoop1.0 Image
   

 * By Thierry Carrez: development environment for Ubuntu-based release
   of OpenStack
   


   Upcoming Events

 * Minnesota OpenStack: Part 2
   
   Jan 07, 2013 – Minneapolis, MN Details
   
 * OpenStack DACH Meetup
    Jan 09, 2013
   – Cologne (Köln), Germany Details
   
 * OpenStack Denver Meetup
   
   Jan 09, 2013 – Denver, CO Details
   
 * OpenStack Users January 2013 meetup
   
   Jan 19, 2013 – Bangalore, India Details
   
 * Openstack Developers Meetup
    Jan 20, 2013 –
   Jerusalem, Israel Details
   
 * FOSDEM’13  Feb 02 –
   03, 2013 – Bruxelles, Belgium Cloud track
   
 * Second Swiss OpenStack User Group Meeting
    Feb 19, 2013 –
   Zurich, Switzerland Details
   


   Other news

 * Details about OpenStack at linux.conf.au 2013
   
 * Grizzly-2 just around the corner
   
 * OpenStack Project Meeting didn’t happen this week


   Welcome new contributors

Celebrating the first patches submitted this week by:

 * Janis Gengeris

/The weekly newsletter is a way for the community to learn about all the 
various activities occurring on a weekly basis. If you would like to add 
content to a weekly update or have an idea about this newsletter, please 
leave a comment./


___
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] How to create vm instance to specific compute node?

[Jay Pipes]

Oh, nice! Thanks for the hint!
-jay

On 01/03/2013 08:03 AM, Day, Phil wrote:
>> Note this is an admin-only ability by default and can oversubscribe the 
>> compute node the instance goes on.
> 
> It is now controlled by a policy (create:forced_host) - so if you want to 
> extend it to other users you can, for example, set up the policy file to 
> control this via a Keystone role
> 
> Phil
> 
> -Original Message-
> From: openstack-bounces+philip.day=hp@lists.launchpad.net 
> [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of 
> Jay Pipes
> Sent: 27 December 2012 22:39
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] How to create vm instance to specific compute node?
> 
> No.
> 
> Use nova boot --availability_zone=nova:hostname where nova: is your 
> availability zone and hostname is the hostname of the compute node you wish 
> to put the instance on.
> 
> Note this is an admin-only ability by default and can oversubscribe the 
> compute node the instance goes on.
> 
> Best,
> -jay
> 
> On 12/27/2012 02:45 PM, Rick Jones wrote:
>> Does the convention of adding --onhost--computenodename to the instanc 
>> name being created still work?
>>
>> rick jones
>>
>> ___
>> 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] Nova - Switch Network mode

[Bruno Parreira]

Even being extremely difficult what would have to be done? we can stop the VMs 
if that helps.

Bruno

Enviado do meu iPad

No dia 03/01/2013, às 21:18, Vishvananda Ishaya  
escreveu:

> This will be extremely difficult. I wouldn't recommend it.  It would probably 
> be easier to make a manual cloudpipe instance instead of having nova manage 
> it. You will just have to do some tweaking of the nwfilter rules of the vm. 
> An even easier solution would be to just make a bastion vm that the 
> collaborators can ssh through.
> 
> Vish
> 
> On Jan 3, 2013, at 12:05 PM, bruno sendas  wrote:
> 
>> Hi,
>> 
>> We have OpenStack Folsom deployed in one computer where there are several 
>> VM's running and we want to instantiate cloudpipe to  provide access to 
>> external collaborators. 
>> 
>> The problem is that the network was deployed using Flat DHCP mode and now we 
>> have to change it to VLAN mode, is it possible to change the networking mode 
>> without having to shutdown the VM's ? Can anybody give the main steps or 
>> tips to change the networking mode in the least disrupting way?
>> 
>> Kind regards,
>> Bruno Sendas ___
>> 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] CY12-Q4 Community Analysis — OpenStack vs OpenNebula vs Eucalyptus vs CloudStack

[Kuo Hugo]

appreciate ~~ Thanks



2013/1/4 Qingye Jiang (John) 

> Hi all,
>
> I would like to let you know that I have just finished my 5th quarterly
> report on comparing the community activities of different open source IaaS
> technologies. "CY12-Q4 Community Analysis — OpenStack vs OpenNebula vs
> Eucalyptus vs CloudStack" is now available on my blog at the following URL.
>
> English Version:
> http://www.qyjohn.net/?p=2733
>
> Chinese Version:
> http://www.qyjohn.net/?p=2731
>
> Best regards,
>
> Qingye Jiang (John)
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
+Hugo Kuo+
tonyt...@gmail.com
+ 886 935004793
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp