Re: [Openstack] NetApp + Openstack folsom

[Diego Parrilla Santamaría]

We have several deployments of customers with StackOps running on NetApp
like a breeze.

Check this document: https://communities.netapp.com/docs/DOC-24892

Cheers
Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Fri, Jun 7, 2013 at 3:18 PM, Alexandre De Carvalho <
alexandre7.decarva...@gmail.com> wrote:

> Hi !
>
>
> I have : 1 controller, 1 compute, 1 block storage and all that this works
> well.  (Ubuntu 12.04 LTS + OpenStack Folsom)
>
> And i would like to add a NetApp iSCSI FAS2020 for this structure. But i
> don't know how and I don't find any document to do it.
>
>
> If you can help me, i'm interested !
>
>
> Thanks for your help !
>
> --
> regards,
> Alexandre
>
>
>
> ___
> 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] [Networking/DNS] Proposal to make Moniker the default for DNS

[Diego Parrilla Santamaría]

+1
 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Mar 19, 2013 at 9:39 AM, Endre Karlson wrote:

> Hi, I would like to propose Moniker as the default for DNS going forwards.
>
> We where picked in a vote by several interested people to be the default
> DNS implementation last year out of the available projects.
>
> The current state of the project is:
> * Several DNSaaS is built on Moniker - HP Cloud's for one.
> * Support for multiple record types A, , SPF, CNAME, NS, MX,
> configurable TTLs.
> * Pluggable storage layer - currently only SQLAlchemy.
> * Pluggable DNS backends that can either be run in a Central process or in
> agents on seperate servers for redundancy
>   - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq
> * Pluggable notification handling - Support for Quantum and Nova via MQ
> notifications.
> * REST API using Flask and JSONSchema.
> * python-monikerclient for bindings / cli.
>
> Github / Code: http://github.com/stackforge/moniker
> Bugs / LP: http://launchpad.net/moniker
> IRC: #openstack-dns
>
> Endre Karlson
>
> ___
> 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][Swift] Cifrado 0.1 Swift CLI available

[Diego Parrilla Santamaría]

> * Asymmetric/Symmetric transparent encryption/decryption of files when
>  uploading/downloading using GnuPG.

KimDotCom must be really scared! Are you going to build an alternative to
MEGA.co.nz based on Swift ? ;-)

Nice stuff man!

Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.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] Suggestions for shared-storage cluster file system

[Diego Parrilla Santamaría]

We have used Gluster for small deployments, but lately we have changed our
mind.  Basically we have bet on Gluster for 2013 because of:

- 10GbE everywhere, and Gluster MUST run in 10GbE (or Infiniband)
- 3.3 release fixes some issues when locking big files: Granular locking
- libgfapi reborn, no more FUSE overhead
- QEMU 1.3 comes with GlusterFS block driver
http://raobharata.wordpress.com/2012/10/29/qemu-glusterfs-native-integration/
- Success cases everywhere

Regarding our tests, NetApp and Nexenta outperforms Gluster, but let's say
we now can live with this performance penalty because cost per bit and
horizontal scalability are really good.

Cheers
Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Feb 19, 2013 at 9:57 PM, Razique Mahroua
wrote:

> Hey Marco,
> have you been able to run some performance test on your Gluster cluster?
>
> Thanks :)
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 18 févr. 2013 à 14:20, Marco CONSONNI  a écrit :
>
> Hello Sam,
>
> I've tried two of them: NFS and Gluster.
>
> Some problems with the former (migration didn't work properly), no problem
> with the latter.
> I vote for Gluster.
>
> Hope it helps,
> Marco.
>
>
>
> On Fri, Feb 15, 2013 at 4:40 PM, Samuel Winchenbach wrote:
>
>> Hi All,
>>
>> Can anyone give me a recommendation for a good shared-storage cluster
>> filesystem?   I am running kvm-libvirt and would like to enable live
>> migration.
>>
>> I have a number of hosts (up to 16) each with 2xTB drives.  These hosts
>> are also my compute/network/controller nodes.
>>
>> The three I am considering are:
>>
>> GlusterFS - I have the most experience with this, and it seems the
>> easiest.
>>
>> CephFS/RADOS - Interesting because glance supports the rbd backend.
>>  Slightly worried because of this though "Important:
>> Mount the CephFS filesystem on the client machine, not the cluster
>> machine."
>> (I wish it said why...)  and "CephFS is not quite as stable as the block
>> device and the object storage gateway."
>>  Lustre - A little hesitant now that Oracle is involved with it.
>>
>> If anyone has any advice, or can point out another that I should consider
>> it would be greatly appreciated.
>>
>> Thanks!
>>
>> 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
>>
>>
> ___
> 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] external dhcp server instead of dnsmasq

[Diego Parrilla Santamaría]

Thanks Vish,

This is something I always forget to ask: I'm curious about the historical
reasons for dnsmasq instead of ISC-DHCP managed with OMAPI, for example.

Cheers
Diego

 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Feb 19, 2013 at 8:37 PM, Vishvananda Ishaya
wrote:

> You cannot have an external dhcp server with openstack. Openstack needs a
> way to know the ip address assigned to a vm to do its listing properly. If
> you don't care about the api returning valid ips there is a possibility of
> using FlatNetworking (not FlatDHCP) to make nova stick the network into a
> bridge and not do any dhcp at all. You could then have an external server
> serving up dhcp ips. I suspect you will probably have to disable security
> groups completely using NoopFirewallDriver driver to get this to work.
>
> As to the reason dhcp-host is not working, I suspect is because we give
> dnsmasq an external hosts file so you probably would need the host
> directive there.
>
> Vish
>
> On Feb 19, 2013, at 4:44 AM, Ritesh Nanda  wrote:
>
> Hope Vish can answer this , what can be the way around to do this.
>
> On Tue, Feb 19, 2013 at 2:01 PM, Razique Mahroua <
> razique.mahr...@gmail.com> wrote:
>
>> Hi,
>> I'm not sure the "dhcp-host" configuration option exists actually. As for
>> having one another host in VLAN mode is something I'd be interested to know
>> as well
>>
>> Regards,
>>
>> *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>> 
>>
>> Le 19 févr. 2013 à 08:05, Ritesh Nanda  a écrit
>> :
>>
>> Hello ,
>>
>> Is it possible to use external dhcp server , instead of dnsmasq .
>> I am using openstack essex, with vlan manager as network,  I have a need
>> where i need to implement dynamic dns,
>> so using dhcp3 as dhcp-server and bind9 as dns is possible.
>>
>> Or is there any way in openstack i can implement dynamic dns in openstack.
>>
>> One more problem which i am facing , dnsmasq has a option to assign
>> static ip to a particular hostname using dhcp-host
>> parameter in dnsmasq config file.
>>
>> i tried it doing by defining  the config file of dnsmasq in nova.conf
>>
>> --dnsmasq_config_file=/etc/nova/dnsmasq.conf
>>
>> then in dnsmasq config file
>>
>> i gave options for a particular subnet.
>>
>>
>> dhcp-range=Tenant-operator,10.0.50.3,10.0.50.254,255.255.255.0,24h
>> dhcp-option=Tenant-operator,6,10.0.50.7
>> domain=operator.com,10.0.50.0/24,local
>> dhcp-host=importantmachine,10.0.50.120
>>
>> these all options are working except dhcp-host.
>>
>> Can anybody help me with this.
>> --
>> * With Regards
>> *
>> * Ritesh Nanda
>> *
>>
>> ***
>> *
>> <http://www.ericsson.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
>>
>>
>>
>
>
> --
> * With Regards
> *
> * Ritesh Nanda
> *
>
> ***
> *
> <http://www.ericsson.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
>
>
>
> ___
> 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] deal with booting lots of instance simultaneously

[Diego Parrilla Santamaría]

Increasing the RPC timeout should help. I have seen this problem in
nova-network in the past. Vish suggestion sounds good.

Recently we launched by mistake 128 VMs in a production environment of a
customer: 0 errors. They are using 12 cores and several gigs for the
nova-network servers with dual 10G pipes. So hardware matters, of course.

My two cents,
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Feb 19, 2013 at 10:09 AM, gtt116  wrote:

>  Hi Diego
>
> Thanks for you reply.
> How many hosts do you have? I have 4 hosts. And in this bug,
> https://bugs.launchpad.net/nova/+bug/1094226, The N is 20. In my
> environment N is about 16.
>
> I found that nova-network is too busy to deal with so many rpc request at
> the same time. The Rabbitmq is strong enough in the scenario.
>
> 于 2013年02月19日 16:54, Diego Parrilla Santamaría 写道:
>
> Hi gtt,
>
>  what does it mean for you 'lots of instance simultaneously'? 100, 1000,
> 1, more?
>
>  We have launched >100 (but less than <1000) simultaneously without any
> issue. Rabbit running in a multicore with several gigs of RAM with out of
> the box configuration.
>
>  Cheers
> Diego
>   --
>  Diego Parrilla
>  <http://www.stackops.com/>*CEO*
> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * <http://www.stackops.com/>
>  *
>
> *
>
>
>
> On Tue, Feb 19, 2013 at 9:35 AM, gtt116  wrote:
>
>>  Hi all,
>>
>> When create lots of instance simultaneously, there will be lots of
>> instance in ERROR state. And most of them are caused by network rpc request
>> timeout. This result is not so graceful.
>>
>> I think it will be better if scheduler keep a queue of creating request.
>> when he find all the hosts are busy enough(compute_node.current_workload
>> reach some value), stop cast the request to host temporarily, until he
>> found some host free enough. In this way, we can make sure booting lots of
>> instances simultaneously results in active instances rather than lots of
>> ERROR instance. but will cause a small weak point, if the top value of
>> current_workload small enough, create instance processing will be slow.
>>
>> Do you have another quick fix?
>>
>> Thanks,
>>
>> --
>> best regards,
>> gtt
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> best regards,
> gtt
>
>
___
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] deal with booting lots of instance simultaneously

[Diego Parrilla Santamaría]

Hi gtt,

what does it mean for you 'lots of instance simultaneously'? 100, 1000,
1, more?

We have launched >100 (but less than <1000) simultaneously without any
issue. Rabbit running in a multicore with several gigs of RAM with out of
the box configuration.

Cheers
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Feb 19, 2013 at 9:35 AM, gtt116  wrote:

>  Hi all,
>
> When create lots of instance simultaneously, there will be lots of
> instance in ERROR state. And most of them are caused by network rpc request
> timeout. This result is not so graceful.
>
> I think it will be better if scheduler keep a queue of creating request.
> when he find all the hosts are busy enough(compute_node.current_workload
> reach some value), stop cast the request to host temporarily, until he
> found some host free enough. In this way, we can make sure booting lots of
> instances simultaneously results in active instances rather than lots of
> ERROR instance. but will cause a small weak point, if the top value of
> current_workload small enough, create instance processing will be slow.
>
> Do you have another quick fix?
>
> Thanks,
>
> --
> best regards,
> gtt
>
>
> ___
> 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] Configuring instances during first boot

[Diego Parrilla Santamaría]

cloud-init and it's variants:

https://help.ubuntu.com/community/CloudInit


 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Tue, Jan 29, 2013 at 10:42 AM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Hi stackers!
>
> Does anyone use initial scripts for resizing disks, adding username and
> hostame to instances during first boot?
> Do you know any example of these utils like cloud-init?
>
> Thanks!
>
> Regards,
> --
> JuanFra
>
> ___
> 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] Error in Horizon or misconfiguration?

[Diego Parrilla Santamaría]

You can change the endpoint type in Horizon:

Modify this file:
/etc/openstack-dashboard/local_settings.py

and add (or edit) this property:
OPENSTACK_ENDPOINT_TYPE=endpoint_type

and endpoint_type can be internalURL, publicURL and adminURL, as usual.

Cheers
Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Thu, Jan 10, 2013 at 1:33 PM, JuanFra Rodriguez Cardoso <
juanfra.rodriguez.card...@gmail.com> wrote:

> Hi guys!
>
> Do you know if this Horizon's bug have been solved? In my fresh
> installation (2012.2.1 from EPEL), it keeps crashing.
> However, remaining operations in dashboard work fine!
>
> [Thu Jan 10 13:20:19 2013] [error] Traceback (most recent call last):
> [Thu Jan 10 13:20:19 2013] [error]   File
> "/usr/lib/python2.6/site-packages/keystoneclient/v2_0/client.py", line 135,
> in _extract_service_catalog
> [Thu Jan 10 13:20:19 2013] [error] endpoint_type='adminURL')
> [Thu Jan 10 13:20:19 2013] [error]   File
> "/usr/lib/python2.6/site-packages/keystoneclient/service_catalog.py", line
> 73, in url_for
> [Thu Jan 10 13:20:19 2013] [error] raise
> exceptions.EndpointNotFound('Endpoint not found.')
> [Thu Jan 10 13:20:19 2013] [error] EndpointNotFound: Endpoint not found.
> [Thu Jan 10 13:20:21 2013] [error] unable to retrieve service catalog with
> token
>
>
> It could be a great chance for my first contribution to Horizon code?
> could I assign myself this bug?
>
> Thanks,
> JuanFra.
>
> ___
> 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] two or more NFS / gluster mounts

[Diego Parrilla Santamaría]

Hi John,

Yes, that's a really good solution. It is exactly what the StackOps
Enterprise Edition offers out of the box.  It's a simpler alternative
assuming you are big enough to have several clusters of compute nodes, and
each cluster with different quality of service preassigned. And it works...
if the scheduler function works.

My proposal about a hierarchy of folders for shared storage comes from
requirements of some customers that want to be able to control the IO on a
tenant basis, and want to use very cheap scalable shared storage.

Let's say that StackOps EE follows now a static approach, and we would like
to have a dynamic one ;-)


Cheers
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Thu, Dec 20, 2012 at 6:37 PM, John Griffith
wrote:

>
>
> On Thu, Dec 20, 2012 at 9:37 AM, JuanFra Rodriguez Cardoso <
> juanfra.rodriguez.card...@gmail.com> wrote:
>
>> Yes, I'm really agree with Diego.
>> It would be a good choice for submitting a blueprint with this storage
>> feature based on tenants.
>>
>> According to current quotas control, it limits the:
>>
>>-
>>
>>Number of volumes which may be created
>>-
>>
>>Total size of all volumes within a project as measured in GB
>>-
>>
>>Number of instances which may be launched
>>-
>>
>>Number of processor cores which may be allocated
>>- Publicly accessible IP addresses
>>
>>
>> Another new feature related to shared storage we had thought about, it's
>> to include an option for choosing if an instance has to be replicated or
>> not, i.e. in a MooseFS scenario, to indicate goal (number of replicas).
>> It's useful for example in testing or demo projects, where HA is not
>> required.
>>
>> Regards,
>>
>> JuanFra.
>>
>> 2012/12/20 Diego Parrilla Santamaría > >
>>
>>> mmm... not sure if the concept of oVirt multiple storage domains is
>>> something that can be implemented in Nova as it is, but I would like to
>>> share my thoughts because it's something that -from my point of view-
>>> matters.
>>>
>>> If you want to change the folder where the nova instances are stored you
>>> have to modify the option in nova-compute.conf  'instances_path':
>>>
>>> If you look at that folder (/var/lib/nova/instances/ by default) you
>>> will see a structure like this:
>>>
>>> drwxrwxr-x   2 nova nova   73 Dec  4 12:16 _base
>>> drwxrwxr-x   2 nova nova5 Oct 16 13:34 instance-0002
>>> ...
>>> drwxrwxr-x   2 nova nova5 Nov 26 17:38 instance-005c
>>> drwxrwxr-x   2 nova nova6 Dec 11 15:38 instance-0065
>>>
>>> If you have a shared storage for that folder, then your fstab entry
>>> looks like this one:
>>> 10.15.100.3:/volumes/vol1/zone1/instances /var/lib/nova/instances nfs
>>> defaults 0 0
>>>
>>> So, I think that it could be possible to implement something like
>>> 'storage domains', but tenant/project oriented. Instead of having multiple
>>> generic mountpoints, each tenant would have a private mountpoint for
>>> his/her instances. So the /var/lib/nova/instances could look like this
>>> sample:
>>>
>>> /instances
>>> +/tenantID1
>>> ++/instance-X
>>> ++/instance-Y
>>> ++/instance-Z
>>> +/tenantID2
>>> ++/instance-A
>>> ++/instance-B
>>> ++/instance-C
>>> ...
>>> +/tenantIDN
>>> ++/instance-A
>>> ++/instance-B
>>> ++/instance-C
>>>
>>> And in the /etc/fstab something like this sample too:
>>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantID1
>>> /var/lib/nova/instances/tenantID1 nfs defaults 0 0
>>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantID2 
>>> /var/lib/nova/instances/tenantID2 nfs
>>> defaults 0 0
>>> ...
>>> 10.15.100.3:/volumes/vol1/zone1/instances/tenantIDN
>>> /var/lib/nova/instances/tenantIDN nfs defaults 0 0
>>>
>>> With this approach, we could have something like per tenant QoS on
>>> shared storage to resell differente storage capabilities on a tenant basis.
>>>
>>> I would love to hear feedback, drawback, improvements...
>>>
>>> Cheers
>>> Diego
>>>
>>>  --
>>> Diego Parrilla
&

Re: [Openstack] two or more NFS / gluster mounts

[Diego Parrilla Santamaría]

mmm... not sure if the concept of oVirt multiple storage domains is
something that can be implemented in Nova as it is, but I would like to
share my thoughts because it's something that -from my point of view-
matters.

If you want to change the folder where the nova instances are stored you
have to modify the option in nova-compute.conf  'instances_path':

If you look at that folder (/var/lib/nova/instances/ by default) you will
see a structure like this:

drwxrwxr-x   2 nova nova   73 Dec  4 12:16 _base
drwxrwxr-x   2 nova nova5 Oct 16 13:34 instance-0002
...
drwxrwxr-x   2 nova nova5 Nov 26 17:38 instance-005c
drwxrwxr-x   2 nova nova6 Dec 11 15:38 instance-0065

If you have a shared storage for that folder, then your fstab entry looks
like this one:
10.15.100.3:/volumes/vol1/zone1/instances /var/lib/nova/instances nfs
defaults 0 0

So, I think that it could be possible to implement something like 'storage
domains', but tenant/project oriented. Instead of having multiple generic
mountpoints, each tenant would have a private mountpoint for his/her
instances. So the /var/lib/nova/instances could look like this sample:

/instances
+/tenantID1
++/instance-X
++/instance-Y
++/instance-Z
+/tenantID2
++/instance-A
++/instance-B
++/instance-C
...
+/tenantIDN
++/instance-A
++/instance-B
++/instance-C

And in the /etc/fstab something like this sample too:
10.15.100.3:/volumes/vol1/zone1/instances/tenantID1
/var/lib/nova/instances/tenantID1 nfs defaults 0 0
10.15.100.3:/volumes/vol1/zone1/instances/tenantID2
/var/lib/nova/instances/tenantID2 nfs
defaults 0 0
...
10.15.100.3:/volumes/vol1/zone1/instances/tenantIDN
/var/lib/nova/instances/tenantIDN nfs defaults 0 0

With this approach, we could have something like per tenant QoS on shared
storage to resell differente storage capabilities on a tenant basis.

I would love to hear feedback, drawback, improvements...

Cheers
Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Thu, Dec 20, 2012 at 4:32 PM, Andrew Holway wrote:

> Good plan.
>
>
> https://blueprints.launchpad.net/openstack-ci/+spec/multiple-storage-domains
>
>
> On Dec 20, 2012, at 4:25 PM, David Busby wrote:
>
> > I may of course be entirely wrong :) which would be cool if this is
> achievable / on the roadmap.
> >
> > At the very least if this is not already in discussion I'd raise it on
> launchpad as a potential feature.
> >
> >
> >
> >
> > On Thu, Dec 20, 2012 at 3:19 PM, Andrew Holway 
> wrote:
> > Ah shame. You can specify different storage domains in oVirt.
> >
> > On Dec 20, 2012, at 4:16 PM, David Busby wrote:
> >
> > > Hi Andrew,
> > >
> > > An interesting idea, but I am unaware if nova supports storage
> affinity in any way, it does support host affinity iirc, as a kludge you
> could have say some nova compute nodes using your "slow mount" and reserve
> the "fast mount" nodes as required, perhaps even defining separate zones
> for deployment?
> > >
> > > Cheers
> > >
> > > David
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Dec 20, 2012 at 2:53 PM, Andrew Holway 
> wrote:
> > > Hi David,
> > >
> > > It is for nova.
> > >
> > > Im not sure I understand. I want to be able to say to openstack;
> "openstack, please install this instance (A) on this mountpoint and please
> install this instance (B) on this other mountpoint." I am planning on
> having two NFS / Gluster based stores, a fast one and a slow one.
> > >
> > > I probably will not want to say please every time :)
> > >
> > > Thanks,
> > >
> > > Andrew
> > >
> > > On Dec 20, 2012, at 3:42 PM, David Busby wrote:
> > >
> > > > Hi Andrew,
> > > >
> > > > Is this for glance or nova ?
> > > >
> > > > For nova change:
> > > >
> > > > state_path = /var/lib/nova
> > > > lock_path = /var/lib/nova/tmp
> > > >
> > > > in your nova.conf
> > > >
> > > > For glance I'm unsure, may be easier to just mount gluster right
> onto /var/lib/glance (similarly could do the same for /var/lib/nova).
> > > >
> > > > And just my £0.02 I've had no end of problems getting gluster to
> "play nice" on small POC clusters (3 - 5 nodes, I've tried nfs tried
> glusterfs, tried 2 replica N distribute setups with many a random glusterfs
> 

Re: [Openstack] Troubleshooting Swift 1.7.4 on mini servers

[Diego Parrilla]

Sorry for my off topic question, it's the first time I heard of swift storage 
servers running an ARM processor. 

I think ARM architectures can be an interesting alternative to replace classic 
computing servers, but swift storage nodes did not catch my attention as a 
valid alternative, until now.

From my perspective, the savings in power consumption and real state in your 
datacenter are minimized if you load your servers with two dozen SATA disks (a 
typical swift node configuration) and a dual 10GbE connection, for example.

May be there are benefits I'm not aware of, but I would really love to hear 
about them :-)

Cheers
Diego

Enviado desde mi iPhone, perdona la brevedad

El 27/10/2012, a las 02:26, Nathan Trueblood  escribió:

> Hey folks-
> 
> I'm trying to figure out what's going wrong with my Swift deployment on a 
> small cluster of "mini" servers.   I have a small test cluster (5 storage 
> nodes, 1 proxy) of mini-servers that are ARM-based.   The proxy is a regular, 
> Intel-based server with plenty of RAM.   The object/account/container servers 
> are relatively small, with 2GB of RAM per node.
> 
> Everything starts up fine, but now I'm trying to troubleshoot a strange 
> problem.   After I successfully upload a few test files, it seems like the 
> storage system stops responding and the proxy gives me a 503 error.
> 
> Here's the test sequence I run on my proxy:
> 
> lab@proxy01:~/bin$ ./swiftcl.sh stat
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass stat
>Account: AUTH_system
> Containers: 5
>Objects: 4
>  Bytes: 47804968
> Accept-Ranges: bytes
> X-Timestamp: 1351294912.72119
> lab@proxy01:~/bin$ ./swiftcl.sh upload myfiles1 /home/lab/bigfile1 
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass upload 
> myfiles1 /home/lab/bigfile1
> home/lab/bigfile1
> lab@proxy01:~/bin$ ./swiftcl.sh upload myfiles2 /home/lab/bigfile1 
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass upload 
> myfiles2 /home/lab/bigfile1
> home/lab/bigfile1
> lab@proxy01:~/bin$ ./swiftcl.sh upload myfiles3 /home/lab/bigfile1 
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass upload 
> myfiles3 /home/lab/bigfile1
> home/lab/bigfile1
> lab@proxy01:~/bin$ ./swiftcl.sh upload myfiles4 /home/lab/bigfile1 
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass upload 
> myfiles4 /home/lab/bigfile1
> home/lab/bigfile1
> lab@proxy01:~/bin$ ./swiftcl.sh upload myfiles5 /home/lab/bigfile1 
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass upload 
> myfiles5 /home/lab/bigfile1
> Object PUT failed: 
> http://172.16.1.111:8080/v1/AUTH_system/myfiles5/home/lab/bigfile1 503 
> Service Unavailable  [first 60 chars of response] 503 Service Unavailable
> 
> The server is currently unavailable
> lab@proxy01:~/bin$ ./swiftcl.sh stat
> swift -A http://proxy01:8080/auth/v1.0 -U system:root -K testpass stat
>Account: AUTH_system
> Containers: 6
>Objects: 5
>  Bytes: 59756210
> Accept-Ranges: bytes
> X-Timestamp: 1351294912.72119
> 
> Here's the corresponding log on the Proxy:
> 
> Oct 26 17:06:52 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/06/52 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0010
> Oct 26 17:07:13 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/13 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0017
> Oct 26 17:07:13 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/13 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0016
> Oct 26 17:07:22 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/22 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0010
> Oct 26 17:07:22 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/22 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0016
> Oct 26 17:07:27 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/27 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0010
> Oct 26 17:07:27 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/27 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0016
> Oct 26 17:07:27 proxy01 proxy-server Handoff requested (1) (txn: 
> tx6946419daba54efe9c2878f8a2a78f88) (client_ip: 172.16.1.111)
> Oct 26 17:07:27 proxy01 proxy-server Handoff requested (2) (txn: 
> tx6946419daba54efe9c2878f8a2a78f88) (client_ip: 172.16.1.111)
> Oct 26 17:07:33 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/33 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0010
> Oct 26 17:07:33 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/33 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0016
> Oct 26 17:07:33 proxy01 proxy-server Handoff requested (1) (txn: 
> tx5f9659f74cb2491f9a63cbb84f680c5c) (client_ip: 172.16.1.111)
> Oct 26 17:07:33 proxy01 proxy-server Handoff requested (2) (txn: 
> tx5f9659f74cb2491f9a63cbb84f680c5c) (client_ip: 172.16.1.111)
> Oct 26 17:07:39 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/39 GET 
> /auth/v1.0/ HTTP/1.0 200 - - - - - - - - 0.0009
> Oct 26 17:07:39 proxy01 proxy-server - 127.0.0.1 27/Oct/2012/00/07/39 GE

Re: [Openstack] Versioning for notification messages

[Diego Parrilla Santamaría]

If you are proposing a new interface to the existing notification system
that could be stable enough to 'survive' multiple versions, then I agree.
The trade-off is we will loose information of the payload, unless somebody
out there have a magic solution for this (and probably the version number
is part of the recipe). But I guess we need this interface. There was
something on the table 2 or 3 summits ago but the notification system did
not evolve a lot (something that surprises me because from the business
perspective Activity auditing is a must-be feature of any IaaS platform).

Talking about ceilometer, I think mixing notifications (activity) and usage
(metrics) is not a good idea. I know people in the community disagree, but
they are different things.

 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Wed, Oct 10, 2012 at 12:02 PM, Day, Phil  wrote:

>  Whilst a version number would allow a consumer to detect that something
> has changed, it doesn’t really help in providing any kind of backward
> compatibility.
>
> Consider the following scenario:  There are a bunch of systems external to
> Nova developed to consume notification messages, and someone introduces a
> change to the notification system that changes the message content.   They
> do the right thing in updating the version number, but all of those
> external systems now need to change as well.   The new version number lets
> them fail explicitly, but it could still have a significant impact on a
> production system.
>
> ** **
>
> Where I’d like to get to make the notification system a formal external
> interface, that has the same degree of stability, version control, and
> rigor around changes that the inbound API has.   
>
> ** **
>
> I would guess that Ceilometer will have some requirement around this ?
>
> ** **
>
> Phil
>
> ** **
>
> *From:* Diego Parrilla Santamaría [mailto:
> diego.parrilla.santama...@gmail.com]
> *Sent:* 10 October 2012 09:18
> *To:* Day, Phil
> *Cc:* David Ripton; openstack@lists.launchpad.net
>
> *Subject:* Re: [Openstack] Versioning for notification messages
>
> ** **
>
> If we want to have a notification system that could handle messages with
> different payloads and different versions, we have two options:
>
> 1) detect the version of the payload in the notification message
> 2) add a version number in the notification message
>
> Option 1 sounds to me like something hard to maintain. Option 2 seems to
> be correct way to do it in the long term.
>
> +1 for a version number in the notification message
>
> Cheers
> Diego
>  -- 
>
> Diego Parrilla
> *CEO*
> *www.stackops.com | * diego.parri...@stackops.com | +34 649 94 43 29| 
> skype:diegoparrilla
> *
> * <http://www.stackops.com/>
>
> **
>
> ** **
>
>
>
> 
>
> On Wed, Oct 10, 2012 at 9:27 AM, Day, Phil  wrote:
>
> Hi All,
>
> I guess I may have mis-stated the problem a tad in talking about version
> numbering.  The notification system is an outbound interface, and my
> interest is in being able to write consumers with some guarantee that they
> won't be broken as the notification message format evolves.
>
> Having a version number gives the client a way to know that it may now be
> broken, but that's not really the same as having an interface with some
> degree of guaranteed compatibility,
>
> Phil
>
>
> -Original Message-
> From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:
> openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of
> David Ripton
> Sent: 09 October 2012 20:59
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Versioning for notification messages
>
> On 10/09/2012 01:07 PM, Day, Phil wrote:
>
> > What do people think about adding a version number to the notification
> > systems, so that consumers of notification messages are protected to
> > some extent from changes in the message contents ?
> >
> > For example, would it be enough to add a version number to the
>
> > messages - or should we have the version number as part of the topic
>
> > itself (so that the notification system can provide both a 1.0 and 1.1
> feed), etc ?
>
> Putting a version number in the messages is easy, and should work fine.
>   Of course it only really helps if someone writes clients that can deal
> with multiple versions, or at least give helpful error messages when they
> get an unexpected version.
>
> I think using separate topics for each ve

Re: [Openstack] Versioning for notification messages

[Diego Parrilla Santamaría]

If we want to have a notification system that could handle messages with
different payloads and different versions, we have two options:

1) detect the version of the payload in the notification message
2) add a version number in the notification message

Option 1 sounds to me like something hard to maintain. Option 2 seems to be
correct way to do it in the long term.

+1 for a version number in the notification message

Cheers
Diego
 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Wed, Oct 10, 2012 at 9:27 AM, Day, Phil  wrote:

> Hi All,
>
> I guess I may have mis-stated the problem a tad in talking about version
> numbering.  The notification system is an outbound interface, and my
> interest is in being able to write consumers with some guarantee that they
> won't be broken as the notification message format evolves.
>
> Having a version number gives the client a way to know that it may now be
> broken, but that's not really the same as having an interface with some
> degree of guaranteed compatibility,
>
> Phil
>
> -Original Message-
> From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:
> openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of
> David Ripton
> Sent: 09 October 2012 20:59
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Versioning for notification messages
>
> On 10/09/2012 01:07 PM, Day, Phil wrote:
>
> > What do people think about adding a version number to the notification
> > systems, so that consumers of notification messages are protected to
> > some extent from changes in the message contents ?
> >
> > For example, would it be enough to add a version number to the
> > messages - or should we have the version number as part of the topic
> > itself (so that the notification system can provide both a 1.0 and 1.1
> feed), etc ?
>
> Putting a version number in the messages is easy, and should work fine.
>   Of course it only really helps if someone writes clients that can deal
> with multiple versions, or at least give helpful error messages when they
> get an unexpected version.
>
> I think using separate topics for each version would be inefficient and
> error-prone.
>
> Inefficient because you'd have to send out multiples of each message, some
> of which would probably never be read.  Obviously, if you're sending out N
> copies of each message then you expect only 1/N the queue performance.
>  Worse, if you're sending out N copies of each message but only 1 of them
> is being consumed, your queue server is using a lot more memory than it
> needs to, to hold onto old messages that nobody needs.
> (If you properly configure a high-water mark or timeout, then the old
> messages will eventually be thrown away.  If you don't, then your queue
> server will eventually consume way too much memory and start swapping, your
> cloud will break, and someone will get paged at 2 a.m.)
>
> Error-prone because someone would end up reusing the notification queue
> code for less idempotent/safe uses of queues, like internal API calls.
> And then client A would pick up the message from topic_v1, and client B
> would pick up the same message from topic_v2, and they'd both perform the
> same API operation, resulting in wasted resources in the best case and data
> corruption in the worst case.
>
> --
> David Ripton   Red Hat   drip...@redhat.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
>
> ___
> 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] A blueprint on dynamic consolidation of virtual machines

[Diego Parrilla Santamaría]

Hi Anton,

really interesting stuff. We are also in very early stages in a research
project to automate VM consolidation.

Most of the studies focus on information taken from power supplies and
physical devices. We are more interested in looking for patterns of
applications usage (database hits, IOPs,  files used...)

What inputs are you using in your algorithms?
Regards
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Fri, Aug 17, 2012 at 10:22 AM, Anton Beloglazov <
anton.belogla...@gmail.com> wrote:

> Hi All,
>
> I've recently submitted a blueprint describing my project of a framework
> for dynamic consolidation of virtual machines for OpenStack:
>
>
> https://blueprints.launchpad.net/nova/+spec/dynamic-consolidation-of-virtual-mforachines<https://blueprints.launchpad.net/nova/+spec/dynamic-consolidation-of-virtual-machines>
>
> If anyone is interested in this topic, it would be great to get any
> feedback or suggestions.
>
> Thanks,
> Anton Beloglazov
>
> ___
> 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] how to set individual gateway for each VLAN or Tenant network?

[Diego Parrilla Santamaría]

It would be great if you can share the code, no matter if it's in Diablo.

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Mon, Jun 11, 2012 at 8:17 PM, Nathanael Burton <
nathanael.i.bur...@gmail.com> wrote:

> dnsmasq supports setting parameters such as the gateway IP and other
> settings based on tag. I have run a patched version of nova-network in the
> Diablo time that used the network DB label field as the network tag in
> dnsmasq. This then allows you to set custom configs by modifying the
> dnsmasq.conf file. This was done with VLANmanager.
>
> Thanks
>
> Nate
> On Jun 11, 2012 2:09 PM, "Lorin Hochstein" 
> wrote:
>
>>
>> On Jun 4, 2012, at 8:22 PM, romi zhang wrote:
>>
>> Hi,
>> ** **
>> I am using VLAN network mode and will connect eth1 and eth2 of my compute
>> node to the LAN Switch, and LAN switch will create individual VLAN IP
>> interface for each Tenant/VLAN and then route to the NAT equipment,through
>> SNAT/DNAT to touch internet. So, that needs I can set the default gateway
>> of each Tenant VLAN to the different IP address of VLAN interface on the
>> switch.
>>
>>
>> I have the same question, I would love to know if you can set the
>> gateways in VLAN mode.
>>
>> ** **
>> For example, my first tenant(auto0Tenant) is at VLAN200/br200/eth1/fix_ip
>> range is 192.168.2.0/28 and second(aotu1Tenant) is
>> VLAN300/br300/eth2/fix_ip_range 192.168.3.0/28, the VLAN interface ip
>> address for them on switch is 192.168.2.9 and 192.168.3.9, I want to set
>> the default gateway of VMs in auto0Tenant to 192.168.2.9 and 192.168.3.9
>> for aotu1Tenant’s VMs.
>> ** **
>> I try to use two methods, the first is to use nova-command:
>> ** **
>> nova-manage network create --label=auto0Tenat --fixed_range_v4=
>> 192.168.2.0/28 --num_networks=1 --gateway=192.168.2.9 --dns1=61.139.2.69
>> --vlan=200 --bridge=br200 --bridge_interface=eth1 --network_size=16
>> --multi_host=T --project_id=5f9281bca6854fe3974a457d81afd78c
>> ** **
>> nova-manage network create --label=aotu1Tenant --fixed_range_v4=
>> 192.168.3.0/28 --num_networks=1 --gateway=192.168.3.9 --dns1=61.139.2.69
>> --vlan=300 --bridge=br300 --bridge_interface=eth2 --network_size=16
>> --multi_host=T --project_id=5f9281bca6854fe3974a457d81afd78c
>> ** **
>> but the result is the newest created VM default gateway is still the IP
>> address of br200 or br300 by the system, that means the factor of “gateway”
>> and “dns1” in nova-mange network command did not work.
>> ** **
>> The second way is to use dnsmasq.conf that Vish told me, that I set just
>> dhcp_option=3,192.168.2.9. Yes it is useful for auto0Tenat VLAN, it can set
>> auto0Tenant gateway to 192.168.2.9, but how to set others at the same time?
>> 
>> ** **
>> Then I tried to use:
>> ** **
>> Interface=vlan200
>> dhcp_option=3,192.168.2.9
>> ** **
>> Interface=vlan300
>> dhcp_option=3,192.168.3.9
>> ** **
>>
>>
>> Does it actually work to specify multiple interfaces in the dnsmasq conf
>> file like that? I would have thought that the second values would override
>> the first ones.
>>
>>
>>  Take care,
>>
>> 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
>>
>>
> ___
> 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] Ceph + OpenStack [HOW-TO]

[Diego Parrilla Santamaría]

great job!
 --
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Sun, Jun 10, 2012 at 11:32 PM, Sébastien Han wrote:

> Hello everyone,
>
> I recently posted on my website an introduction to ceph and the
> integration of Ceph in OpenStack.
> It could be really helpful since the OpenStack documentation has not dealt
> with it so far.
>
> Feel free to comment, express your opinions and share your personal
> experience about both of them.
>
> Here the link to the article:
> http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
>
> Regards.
>
> Sébastien Han.
>
>
>
> ___
> 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] ZFS/ZVol + iscsi for volume

[Diego Parrilla Santamaría]

Hi Nicolas,

have you seen this?
https://github.com/StackOps/nova/blob/master/nova/volume/san.py

It has a Solaris implementation that works on top ZFS. And it works. We
modified it work with Nexenta in Diablo:
https://github.com/StackOps/nova/blob/stable/diablo/nova/volume/san.py

Cheers
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Sun, Jun 10, 2012 at 8:07 PM, Nicolas de BONFILS <
openst...@nicolas2bonfils.com> wrote:

> **
>
> Hi Diego,
>
> Thanks for your ideas about vm storage.
> In my proposal/question, I got in mind (for now) volume more than vm
> storage (with the zfs property allowing nfs sharing, I believe that vm
> storage can already be done with zfs backend).
>
> --- Nicolas
>
> On 2012-06-10 17:58, Diego Parrilla Santamaría wrote:
>
> Nicolas,
> it makes a lot of sense what you want to do. ZFS+iSCSI is a perfect fit
> for vm storage, some other IaaS solutions already use this combination (and
> I have developed some). Keep in mind that Nexenta is only a distro based
> upon OpenSolaris: OpenIndiana, FreeBSD... there are a lot of options with
> ZFS.
> There are several things you should consider to implement this feature:
> 1) The code that matters is mostly in nova/virt/libvirt/connection.py for
> libvirt
> 2) You need to implement a new storage type: iscsi (
> http://libvirt.org/storage.html#StorageBackendISCSI)
> 3) You need to implement a feature to block-copy the source image to the
> backend iscsi storage
> 4) _cache_image method and most of _create_image should be developed
> thinking in 3)
> I think the only reason to implement this feature is to develop a highly
> scalable storage system for instances, so a single storage system does not
> make sense. It should be able to manage a list storage systems as a pool
> and load balance them.
> Some quick thoughts, good luck!
> Diego
>
>  --
>  Diego Parrilla
> *CEO*
> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * <http://www.stackops.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] ZFS/ZVol + iscsi for volume

[Diego Parrilla Santamaría]

Nicolas,

it makes a lot of sense what you want to do. ZFS+iSCSI is a perfect fit for
vm storage, some other IaaS solutions already use this combination (and I
have developed some). Keep in mind that Nexenta is only a distro based upon
OpenSolaris: OpenIndiana, FreeBSD... there are a lot of options with ZFS.

There are several things you should consider to implement this feature:
1) The code that matters is mostly in nova/virt/libvirt/connection.py for
libvirt
2) You need to implement a new storage type: iscsi (
http://libvirt.org/storage.html#StorageBackendISCSI)
3) You need to implement a feature to block-copy the source image to the
backend iscsi storage
4) _cache_image method and most of _create_image should be developed
thinking in 3)

I think the only reason to implement this feature is to develop a highly
scalable storage system for instances, so a single storage system does not
make sense. It should be able to manage a list storage systems as a pool
and load balance them.

Some quick thoughts, good luck!
Diego

 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Sun, Jun 10, 2012 at 11:15 AM, Nicolas de BONFILS <
openst...@nicolas2bonfils.com> wrote:

> **
>
> Hi Stackers,
>
> I got an idea/question about iscsi volume.
>
> Actually the workflow is :
>
>
>1. create an LVM pool
>2. create a volume in this pool (with nova command or horizon UI)
>3. share it with an iscsi target (the compute/volume node)
>4. attach it with an iscsi initiator (the VM)
>
> I use zfs for other project, and I'm very interested in using it
> everywhere (when possible). One functionality zfs bring is zvol : it allows
> to create a block device from a zfs pool (a zfs property allow to share
> this device with iscsi).
> With this, a new workflow will be :
>
>1. create a zfs pool (zpool create  )
>2. create a zvol block device (zfs create -V 
>/)
>3. set the zfs property to share it with iscsi (zfs set shareiscsi=on
>/)
>4. attach it with an iscsi initiator (the VM)
>
> From what I read, the Nexenta guys do a lot of work around zfs, but for
> volume use I only found code to plug a Nexenta san (I do not have the
> hardware to build a san), but no solution to use zfs drive/pool directly.
> So my 2 questions are :
>
>1. are some people interested in it ?
>2. does it seem possible to do it (maybe some one already try) ? Nova
>volume driver 
> [github.com<https://github.com/openstack/nova/blob/master/nova/volume/driver.py>]
>got subclasses for specific cases, maybe a new zfs one.
>
>
>
> Please discuss, submit ideas !
>
> --- Nicolas
>
> ___
> 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] Where to add the performance increasing method in openstack

[Diego Parrilla]

Hi Sandy,

Where is your VM I/O based scheduler published? We are also working on smart 
schedulers.

Cheers
Diego

Enviado desde mi iPhone, perdona la brevedad

El 24/05/2012, a las 15:10, Sandy Walsh  escribió:

> Hi!
> 
> You would want to report this information to the Scheduler (probably via the 
> db) so it can make more informed decisions. A new Weight Function in the 
> scheduler would be the place to add it specifically.
> 
> We currently track the number of VM I/O operations being performed on each 
> Compute node for this (build, resize, migration, etc) but nothing within the 
> guest itself. Could be handy for certain verticals. 
> 
> Hope it helps,
> Sandy
> 
> From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net 
> [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf 
> of sarath zacharia [sarathzacha...@gmail.com]
> Sent: Thursday, May 24, 2012 1:48 AM
> To: Nagaraju Bingi
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Where to add the performance increasing method in 
> openstack
> 
> Hi
>   Yes , We are monitoring the loads on the instances in each node and 
> next instances will create in most suitable node ie, 
>  node have less load
> 
> Regards ,
> 
> Sarath Zacharia
>  
> 
> On Wed, May 23, 2012 at 6:51 PM, Nagaraju Bingi 
>  wrote:
> Hi,
> 
>  
> 
> Do you mean that your program would monitor the Openstack Instances and check 
> the performance and load of nodes according to the number of different 
> application running in each instance?
> 
> Your program will tell you that which Instance is the best suitable to deploy 
> your new application.
> 
>  
> 
> Please let me know if I understood correctly.
> 
>  
> 
> Regards,
> 
> Nagaraju B
> 
>  
> 
>  
> 
> From: openstack-bounces+nagaraju_bingi=persistent.co...@lists.launchpad.net 
> [mailto:openstack-bounces+nagaraju_bingi=persistent.co...@lists.launchpad.net]
>  On Behalf Of sarath zacharia
> Sent: Wednesday, May 23, 2012 10:57 AM
> To: openstack@lists.launchpad.net
> Subject: [Openstack] Where to add the performance increasing method in 
> openstack
> 
>  
> 
> 
> 
> Hi ,
> 
>   We created an performance increasing programe for cloud 
> application. 
> 
> This programe will check the performance and load of nodes according
> 
> to the number of different application running in each node of our cloud 
> environment and
> 
> it will give which node is more suitable for deploying the next application 
> in cloud. 
> 
> In which service we have to modify in openstack for implementing this 
> algoritham ? 
> 
>  
> 
> note : now our code is in java how we can connect to the nova development 
> environment
> 
>  
> 
> Yours Sincerly
> 
>  
> 
> Sarath Zacharia
> 
>  
> 
>   
> 
> DISCLAIMER == This e-mail may contain privileged and confidential 
> information which is the property of Persistent Systems Ltd. It is intended 
> only for the use of the individual or entity to which it is addressed. If you 
> are not the intended recipient, you are not authorized to read, retain, copy, 
> print, distribute or use this message. If you have received this 
> communication in error, please notify the sender and delete all copies of 
> this message. Persistent Systems Ltd. does not accept any liability for virus 
> infected mails.
> 
> 
> 
> 
> -- 
> with regards
> 
> Sarath !
> ___
> 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] SAN and Fibrechannel with OpenStack

[Diego Parrilla Santamaría]

Hi Wolfgang,

latest versions of our distro supports NFS as backend storage for
instances, volumes and images. Basically a zone shares the same NFS
mountpoint for instances and another mountpoint for volumes, and I guess it
does not differ a lot from what you want to do with FC or iSCSI.

It's in our immediate roadmap to use FC and iSCSI instead of NFS, but may
be you can give a try to our NFS stuff until then ;-)

Cheers
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Wed, May 16, 2012 at 11:05 AM, Wolfgang Hennerbichler <
wolfgang.hennerbich...@risc-software.at> wrote:

> dear openstack godfathers;
>
> I do plan to migrate from crappy vmware and some ibm based cloud stack to
> openstack and kvm. here's the thing: I am lucky enough to have decent
> hardware, all the compute nodes are interconnected via fibre channel.
> so I don't want and don't need  iscsi. do you think I can make it with
> something like clvm? I read through the docs of openstack, but I am not
> really sure now if I can make clvm fly without hacking around in openstack
> (and nova-volume) too much, especially when it comes to live migration and
> so on...
>
> I realize OpenStack was not built for SAN and FC, but I would really like
> to hear your opinions on that.
> Thanks,
>
> Wolfgang
> --
> DI (FH) Wolfgang Hennerbichler
> Software Development
> Unit Advanced Computing Technologies
> RISC Software GmbH
> A company of the Johannes Kepler University Linz
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help   : 
> https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Using Nova APIs from Javascript: possible?

[Diego Parrilla Santamaría]

Awesome Javier

Anxiously waiting for a meeting with you guys to see your progress!

Cheers
Diego
 --
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Thu, Apr 26, 2012 at 9:50 AM, javier cerviño  wrote:

> Hi all,
>
> I'm glad to hear that there's a lot of interest in the implementation
> of Openstack JavaScript clients. Actually, in my group we're
> developing a "single page" application developed entirely in
> JavaScript, that widely supports Nova and Keystone APIs.  This work is
> part of a European Project called FI-Ware (http://www.fi-ware.eu/), in
> which we are currently using Openstack APIs.
>
> We've modified Nova and Keystone installations by adding CORS support.
> We did it by implementing a kind of filter on their APIs. For doing
> this we used Adam's implementation
> (https://github.com/adrian/swift/tree/cors), and we adapted it to Nova
> and Keystone components. We also developed a JS library
> (http://ging.github.com/jstack/) that can be used by both web and
> Node.js applications, for example. This library aims to provide same
> functionalities as python-novaclient, adding support for Keystone API.
>
> And finally we are copying Openstack horizon functionality, using JS
> library and other frameworks such as jQuery and Backbone.js to
> implement the web application. This web application is an
> "early-stage" work, but we will probably publish it by the end of this
> week. I will let you know the github link.
>
> We didn't find much problems with CORS implementation and support in
> browsers.  For the time being, according to our experiments, the only
> web browser that is not usable at all with this technology is Internet
> Explorer, but we have tried it in Google Chrome, Safari and Firefox as
> well and we didn't have any problems.
>
> Cheers,
> Javier Cerviño.
>
> On 26 April 2012 06:28, Nick Lothian  wrote:
> >
> >
> > On Thu, Apr 26, 2012 at 5:49 AM, Adam Young  wrote:
> >>
> >> Let me try to summarize:
> >>
> >> 1.  If you are running from a web browser,  post requests to hosts or
> >> ports other than the origin are allowed,  but the headers cannot be
> >> modified.  This prevents the addition of the token from Keystone to
> provide
> >> single sign on.
> >>
> >> 2.  There are various browser side technologies (JSONP, CORS) that get
> >> around this limitation, but they are typically not enabled,  and can be
> >> considered security issues.  While implementing these might require
> support
> >> from teh Openstack server,  they are fundamentally browser decisions.
> >>
> >
> > This is inaccurate. JSONP is supported by all browsers since ~Netscape
> 4.0.
> >
> > CORS is supported by all modern browsers: IE > 8, Firefox > 3.5, Chrome
> > 3,
> > Safari > 4
> > (See
> http://en.wikipedia.org/wiki/Cross-origin_resource_sharing#Browser_support
> ).
> > Additionally, CORS support is not a browser decision - the server has to
> > EXPLICITLY opt-in to support it.
> >
> > Obviously CORS support *can* be a security issue - that is why it is
> > disabled unless the server enables it.
> >
> > I do not believe that CORS support adds any additional security issues
> above
> > what the OpenStack APIs already face. Specially, the most common problem
> > (CSRF) is not an issue here because the APIs are not authorised on a
> session
> > basis.
> >
> >  [snip]
> >>
> >>
> >> I've been working on Single Sign on Issues for another project for the
> >> past year and a half.  Here's a couple things I've learned.
> >>
> >>
> >> Kerberos is designed to solve this problem.  It has the benefit of being
> >> integrated into the browser.  Where Kerberos fails is that:  typically
> it
> >> only allows a single authentication provider (KDC in Kerberso speak)
> and it
> >> does not work well with Firewalls.
> >>
> >> The only crytographically secure way to authenticate on the web that can
> >> get around the firewall issue is Client side X509 certificates.  This
> is the
> >> foundation for https://blueprints.launchpad.net/keystone/+spec/pki.
>  This
> >> could, in theory, work in with OAuth, OpenID,  or some other distributed
> >> authorization service,  or we could embed the authorization information
> >> right into the Certitificate, which is what I suggest we do

Re: [Openstack] Encrypted virtual machines

[Diego Parrilla Santamaría]

+1


> >From a security stand point I am curious what you see the benefit as?
>
> On Thu, Apr 26, 2012 at 8:53 AM, Michael Grosser 
> wrote:
> > Hey,
> >
> > I'm following the openstack development for some time now and I was
> > wondering if there was a solution to spin up encrypted virtual machines
> by
> > default and if it would be a huge performance blow.
> >
> > Any ideas?
> >
> > Cheers Michael
> > ___
> > 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] Quantum deployment on Essex

[Diego Parrilla]

Hi Emilien from the Valley,

Check the code from the stackops-agent and the novnc builder, we had to change 
to the cloudbuilders code. We can work on that next week if I can survive to 
the jetlag.

Go and enjoy of The Night of Madrid, we will work on that next week ;-)

Diego 

Enviado desde mi iPad

El 20/04/2012, a las 12:22, OpenStack-Lists  
escribió:

> Hi everyone,
> 
> 
> My name is Emilien, I'm a french student in University and I'm working
> on OpenStack for a internship project.
> 
> 
> I'm working on Quantum deployment at this time, and I would like to
> share with you my work.
> 
> I have two physicals servers for "playing", and I've setup a dual-node
> infrastructure with Essex on Ubuntu 12.04.
> 
> Server 1 :
> 
> Ubuntu 12.04
> 
> All nova services, Glance, Horizon, Keystone and Quantum-agent (coming
> soon).
> 
> Two Nic cards : one public network, one private network.
> 
> 
> Server 2 :
> 
> Ubuntu 12.04
> 
> Nova-compute & Quantum-agent (coming soon)
> 
> Two Nic cards : one public network, one private network.
> 
> 
> For the installation, I've followed differents documentations :
> 
> -
> http://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolin
> 
> -
> http://cssoss.files.wordpress.com/2011/11/openstackbookv2-0_csscorp.pdf
> 
> - Official documentation of OpenStack
> 
> 
> I met a lot of troubles during the deployment (and it's only the
> beginning I think), so I would like if someone here has tried to setup
> Quantum, and which use case he did.
> 
> 
> My goal is to use Open-vSwitch plugin and to try QoS applied to the VMs.
> For exemple, each tenant has each QoS policy. This is actually a
> Proof-of-concept, and this is not fixed !
> 
> 
> I can say now what is working and not :
> 
> - All nova services : Yes, without VNC access (I have a 404 error, and I
> will fix it next week I think).
> - Glance : Yes
> - Keystone : Yes
> - Horizon : Yes (without Swift & Quantum plugins)
> - Quantum : In progress : I've tried to setup Quantum-server in a VM for
> pre-production, and I met a lot of troubles but now, it seems ready for
> testing Monday with Open-vSwitch
> - Open-vSwitch : I don't know which interface to connect on physical
> ETH : public ? private ? If someone can help me to this subject...
> 
> I want to precise that all my services are running with MySQL
> connection.
> 
> 
> 
> Maybe some people is interesting about my work, and please don't
> hesitate to contact me.
> 
> 
> I can of course share my confs files, or anything else.
> 
> 
> Best regards
> 
> 
> -- 
> Emilien Macchi
> Skype : memilien69
> Twitter : EmilienMacchi
> Website : http://my1.fr
> 
> 
> ___
> 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] control user quota

[Diego Parrilla Santamaría]

You can set quotas per tenant. If you have Horizon installed may be you can
modify quotas in the System Panel.

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Thu, Apr 12, 2012 at 4:27 PM, Xin Zhao  wrote:

> Hello,
>
> I try to assign quota to individual users, to control how many instances
> each user can run concurrently. But I don't see a doc describing how to do
> that. I use diablo release.
> Any help or doc pointer will be greatly appreciated.
>
> Xin
>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help   : 
> https://help.launchpad.net/**ListHelp<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] Error Unable to list users: [Errno 110] ETIMEDOUT

[Diego Parrilla Santamaría]

Sounds like you have access to keystone, but you don't have access to
nova-api...

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Thu, Apr 12, 2012 at 2:56 PM, Lucian Thomaz wrote:

>  Hi folks,
> I have a diablo installation with Dashboard and I'm having the following
> error when I try access Tenants or Users on Dashboard:
>
> Error  Unable to get tenant info: [Errno 110] ETIMEDOUT
>
> Error  Unable to list users: [Errno 110] ETIMEDOUT
>
> Has anyone had this problem?
>
>
> *Lucian Thomaz*
>
> ___
> 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] Laptop Demo Environment

[Diego Parrilla]

Have you tried stackops single node deployment? Now you don't need internet 
access.

You can download it from www.stackops.org


Enviado desde mi iPhone, perdona la brevedad

El 10/04/2012, a las 13:38, Lance Haig  escribió:

> Hi All,
> 
> I am starting to build a laptop demo environment to be able to showcase OS to 
> customers without having to get access to the outside world from their 
> meeting rooms.
> 
> My intention is to use kvm on my laptop and then build the environment from 
> scratch.
> 
> My last interaction with OS was during my course at Rackspace in Feb.
> 
> Has anyone done something similar to this and is willing to share a config?
> 
> Is Ubuntu still the preferred distribution for running OS on?
> 
> Thanks
> 
> Lance
> 
> --
> This message was scanned by Better Hosted and is believed to be clean.
> http://www.betterhosted.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

___
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 immaturity

[Diego Parrilla Santamaría]

Immaturity of a platform is something you can easily fix paying the right
fee to your favorite analyst firm.

Seriously, Openstack is an open platform and an open community. This means
problems and issues are open to discuss to everyone. Propietary platforms
issues are rarely disclosed, and they look more mature. And believe me, I
have used most of them and Openstack is not more unstable (or stable) than
others.

Anyway, it's time to move the stack from 'devs' to 'ops'. When somebody
says 'you have to install the development version to fix this' instead of
'you have to follow this procedure on the stable version', you cannot
imagine the damage made to Openstack Nova. It's painful, but it's the only
way to have a robust platform. Let's forget about 'you will have it in the
next release': we are not Microsoft. This is real, not vapourware.

My two cents
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han wrote:

> Hi everyone,
>
> According to the statement of this article from Gartner group
> http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/
>  Openstack is a
> highly immature platform.
> But why? What's make Openstack so immature?
>
> Any comments on that?
>
> Thank you in advance :)
>
>
> ___
> 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] Instance fails to spawn when instance_path is nfs mounted

[Diego Parrilla Santamaría]

We use nfs backed instances a lot, and this problem normally has to do with
wrong permission management in your filer and/or client.

Check if not only root can write on the nfs share (specially libvirt user).

Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**




On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे <
mandarv...@gmail.com> wrote:

> I saw an old question posted here :
> https://answers.launchpad.net/nova/+question/164689
>
> But I am not trying live migration.
>
> I have nfs mounted instances_path - so when I try to spawn an instance I
> run into the above errors. Especially following :
>
> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 372, in
> createWithFlags
> 40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
> libvirtError ('virDomainCreateWithFlags() failed', dom=self)
> 40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
> Process exited while reading console log output: chardev: opening
> backend "file" failed
>
> But as you can see below, several files are created in this folder, so I
> am not sure if mine if permissions issue (Else none of the files would
> get created) The problem is reported when libvirt tries to write to
> console.log (File itself is created with correct permissions - just that
> this is zero byte file)
>
> mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
> total 10944
> drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
> drwxrwxrwx 4 root   root4096 2012-04-03 05:42 ../
> -rw-rw 1 mandar libvirtd   0 2012-04-03 05:42 console.log
> -rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
> -rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
> -rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
> -rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
>
> I'm suspecting :
> https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
> But I the above doesn't show itself in non-NFS setup
>
> Please suggest !!!
>
> -Mandar
>
>
> ___
> 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] regarding this Message #09165 (VNC error with latest version of Firefox)

[Diego Parrilla Santamaría]

Hi Anthony,

yes your fix worked like a charm. We have change the novnc version to the
cloudbuilders one in our distro. The nova-manage service command returns
that novnc-console status as disabled, but it's a minor bug. We also had
some problems with numpy, but now it's working.

I have attached a preview version of the distro with support for the novnc
from cloudbuilders (plus some backports from horizon essex version we have
been working on) if anybody wants to give it a try: it has not been fully
tested, so any feedback is welcomed.

http://dl.dropbox.com/u/527582/iso/stackops-0.4-b1279-d20120329.iso

Cheers
Diego

-- 
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*




On Wed, Mar 28, 2012 at 8:23 PM, Anthony Young
wrote:

> In diablo, nova shipped its own websocket proxy, which had some browser
> compatibility issues due to eventlet's out-dated websocket implementation.
>  For this reason, in essex we replaced nova-vncproxy with one more directly
> based on noVNC's websocket proxy.  Docs for the current proxy may be found
> here:
> https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst
>
> At the time of diablo release, I had an early version of the current proxy
> working against stable/diablo here:
> https://github.com/cloudbuilders/noVNC/branches/diablo - devstack's
> stable/diablo shows how to use that branch.
>
> I just ran the branch mentioned above against diablo + Firefox 11 - seems
> to work.  I would expect the 'official' diablo vnc proxy to have browser
> compat issues, though I have not tried your exact configuration.
>
> Anthony
>
> On Wed, Mar 28, 2012 at 6:09 AM, Staicu Gabriel 
> wrote:
>
>> Hi Diego,
>>
>> I observed the same behavior as you.
>> I am using the latest packages from http://ops.rcb.me/packages.
>> Everything works fine except the connection to vnc console from the
>> latest firefox (11.0) on linux. I tried also with firefox 11.0 from win7
>> and the error is the same.
>> What workaround I found till now is to use firefox (10.0.3) which works
>> ok.
>>
>> Regards,
>> Gabriel
>>
>> ___
>> 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] regarding this Message #09165 (VNC error with latest version of Firefox)

[Diego Parrilla Santamaría]

Yes, it's working.

The trick is to shutdown nova-vncproxy and use the command:

utils/nova-wsproxy.py --flagfile $NOVA_CONF --web . 6080

and install python-numpy package.

We are trying to package in the distro, we have some versioning clash with
some packages. We hope we will release the new fixed distro asap.

Regards
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>



On Thu, Mar 29, 2012 at 5:23 PM, Andrea Federico Grisotto <
andrea.griso...@gmail.com> wrote:

> I tried to use the cloudbuilders branch for diablo but it doesn't work
> with firefox 11 or chrome 18.
> Diego, does it works for you?
>
>
> 2012/3/29 Diego Parrilla Santamaría 
>
>> Thanks Anthony,
>>
>> we use the 'official' noVNC from https://github.com/openstack/noVNC in
>> our distro. We are going to make a new build pulling from cloudbuilders'
>> repository and let's see how it works.
>>
>> Cheers
>> Diego
>> --
>> Diego Parrilla
>> <http://www.stackops.com/>*CEO*
>> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
>> skype:diegoparrilla*
>> * <http://www.stackops.com/>
>> *
>>
>> *
>>
>>
>>
>> On Wed, Mar 28, 2012 at 8:23 PM, Anthony Young <
>> sleepsonthefl...@gmail.com> wrote:
>>
>>> In diablo, nova shipped its own websocket proxy, which had some browser
>>> compatibility issues due to eventlet's out-dated websocket implementation.
>>>  For this reason, in essex we replaced nova-vncproxy with one more directly
>>> based on noVNC's websocket proxy.  Docs for the current proxy may be found
>>> here:
>>> https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst
>>>
>>> At the time of diablo release, I had an early version of the current
>>> proxy working against stable/diablo here:
>>> https://github.com/cloudbuilders/noVNC/branches/diablo - devstack's
>>> stable/diablo shows how to use that branch.
>>>
>>> I just ran the branch mentioned above against diablo + Firefox 11 -
>>> seems to work.  I would expect the 'official' diablo vnc proxy to have
>>> browser compat issues, though I have not tried your exact configuration.
>>>
>>> Anthony
>>>
>>> On Wed, Mar 28, 2012 at 6:09 AM, Staicu Gabriel <
>>> gabriel_sta...@yahoo.com> wrote:
>>>
>>>> Hi Diego,
>>>>
>>>> I observed the same behavior as you.
>>>> I am using the latest packages from http://ops.rcb.me/packages.
>>>> Everything works fine except the connection to vnc console from the
>>>> latest firefox (11.0) on linux. I tried also with firefox 11.0 from win7
>>>> and the error is the same.
>>>> What workaround I found till now is to use firefox (10.0.3) which works
>>>> ok.
>>>>
>>>> Regards,
>>>> Gabriel
>>>>
>>>> ___
>>>> 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] regarding this Message #09165 (VNC error with latest version of Firefox)

[Diego Parrilla Santamaría]

Thanks Anthony,

we use the 'official' noVNC from https://github.com/openstack/noVNC in our
distro. We are going to make a new build pulling from cloudbuilders'
repository and let's see how it works.

Cheers
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Wed, Mar 28, 2012 at 8:23 PM, Anthony Young
wrote:

> In diablo, nova shipped its own websocket proxy, which had some browser
> compatibility issues due to eventlet's out-dated websocket implementation.
>  For this reason, in essex we replaced nova-vncproxy with one more directly
> based on noVNC's websocket proxy.  Docs for the current proxy may be found
> here:
> https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst
>
> At the time of diablo release, I had an early version of the current proxy
> working against stable/diablo here:
> https://github.com/cloudbuilders/noVNC/branches/diablo - devstack's
> stable/diablo shows how to use that branch.
>
> I just ran the branch mentioned above against diablo + Firefox 11 - seems
> to work.  I would expect the 'official' diablo vnc proxy to have browser
> compat issues, though I have not tried your exact configuration.
>
> Anthony
>
> On Wed, Mar 28, 2012 at 6:09 AM, Staicu Gabriel 
> wrote:
>
>> Hi Diego,
>>
>> I observed the same behavior as you.
>> I am using the latest packages from http://ops.rcb.me/packages.
>> Everything works fine except the connection to vnc console from the
>> latest firefox (11.0) on linux. I tried also with firefox 11.0 from win7
>> and the error is the same.
>> What workaround I found till now is to use firefox (10.0.3) which works
>> ok.
>>
>> Regards,
>> Gabriel
>>
>> ___
>> 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] VNC error with latest version of Firefox

[Diego Parrilla Santamaría]

Hi folks,

yesterday we started to see this error when we tried to open a VNC console
with Firefox 11.0:

Websock error:[object event]

and in the error console we have:

Fecha y hora: 27/03/12 13:03:42
Error: Firefox no puede establecer una conexión con el servidor en
ws://A.B.C.D:6080/data?host=hostignore&port=portignore&token=dbf34158-e391-4d5e-839d-a004f66129a2.
Archivo de origen: http://A.B.C.D:6080/include/websock.js
Línea: 255

(Translation: Firefox cannot establish a connection to the server in
ws://...)

It fails with Mac and Linux.

We have tried with Safari on Mac and it works.

Anybody has seen this recently? Any workaround?

Cheers
Diego

P.D.: We are working on the stable branch of Diablo.

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.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] Specification of nova-diagnostics

[Diego Parrilla Santamaría]

I'm not familiar with nova-diagnostics, but we use collectd to gather
information about each virtual machine running in KVM. We get information
about cpu usage, memory, disk io, and network io per instance. Obviously
it's not nicely integrated with nova commands, but it works in our
deployments. And it comes in the distro by default.

Let me know if I can help you in this blueprint: the only reason now in our
distro to use collectd is kvm instances performance. If we can get from
nova we should go that way in the future.

Cheers
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*



On Mon, Mar 26, 2012 at 6:06 PM, Leander Bessa  wrote:

> Hello,
>
> I've been trying to implement the nova-diagnostics command  for libvirt.
> I'm using the devstack installation on ubuntu 12.04. So far i've managed to
> gather information regarding CPU, IO (network and disks). The memory
> reading only works with the virsh command and does not report the actual
> memory usage.  As pointed out to me previously, i've been looking at the
> implementation of nova-diagnostics for the xenapi in order to try and
> figure out how to supply the data back to openstack. However, i can not
> make any sense of it. All i know is that it returns a set of keys with
> values, which i suppose represent the values of the readings. What i wish
> to know is if there's any document or specification which i can read which
> defines what nova-diagnostics should return and under what format.
>
>
> Regards,
>
> Leander
>
> ___
> 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] KVM disk performance

[Diego Parrilla]

Have you tried virtio for storage?

http://www.linux-kvm.org/page/Virtio


Enviado desde mi iPhone, perdona la brevedad

El 26/03/2012, a las 14:59, Martin van Wilderen - JDN BV  
escribió:

> Hi List,
> 
> I have a question about KVM disk performance. We are using Openstack Nova on 
> three machines. These machines have a SSD drive with a dd write performance 
> of about 130mb/s
> 
> Within the instance the write performance is down to about 5 mb/s. When using 
> the allocate trick (dd zero to disk before newfs) we get a performance of 20 
> mb/s.
> 
> Things a have tried but don't give any extra results are:
> - Settings the disklayout from qcow2 to raw
> - Settings the cache type in libvirt.xml (writeback, writethrough, none)
> - Switching KSM on and off.
> - Tested with different guests OS, Linux, FreeBSD, Windows.
> 
> Is there someone who had some extra info i can check? Or are there more 
> people with this issue?
> 
> Snippet from libvirt.xml
> 
> 
> 
> 
> Kind regards,
> 
> Martin
> ___
> 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] Network Connectivity issue

[Diego Parrilla Santamaría]

Hi Nicolas, thanks for using our distro!

Just to summarize:
- Single node
- Management network: 192.168.163.0/25 = 192.168.163.1 to 192.168.163.126.
Let's assume gateway = 192.168.163.1
- Service Network: 192.168.163.128/25 = 192.168.163.129 to 192.168.163.254.
gateway should be = 192.168.163.129

If you wan to ping from the service network to a host in the management
network (and it's not the single node) you need a route to that network. Or
you can configure your system to use the Management Network as the public
network. Then you will reach your hosts.

If you are using FlatDHCP, may be you can configure the smart installer to
use as the service network a subset (not a subnet) of the management
network. It's a dirty hack (I prefer to split networks always) we did in
the past...

For example if you want to setup a little lab in your lapto with the distro
you can use this settings:
- Single node
- Management network: 192.168.10.0/24 (this is my network, use yours)
- Service Network: 10.0.0.0/24
- Public Network (floating range): 192.168.10.64/28 (and of course I don't
have any host in this subnet)

With this configuration floating IPs will reach hosts in the management
network.

Cheers!
Diego


-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Thu, Mar 22, 2012 at 3:47 PM, Nicolas Odermatt wrote:

> Hello guys, I am dealing with a strange phenomenon my StackOps environment.
>
> The thing is like this:
> I am running a single-node stackops deployment in a little /25 network.
> The installation and the few configurations I had to do afterwards went
> just fine, no problems so far. I was also able to upload an image to glance
> and to start an instance using euca2ools. I authorized the necessary port
> for ssh, allowed icmp and then connected to the instance with ssh.
> Afterwards I checked the instance's connection to the internet, which was
> up and running. Now to my so called "strange phenomenon": Although I am
> able to ping my stackops-node, public ip adresses (e.g 8.8.8.8) and in
> spite the fact that name resolving works as well, I can't ping a Client
> machine in my local area network. My stackops-node has the ip-address
> 192.168.163.20/25, the instance has the ip-address(192.168.163.130/25)
> and the client has the ip-address 192.168.163.5/25.
>
> I can't think of an approach to this problem, as I have enabled ssh and
> icmp and the connection between Client and stackops-node exists.
> Is it possible that I might have forgott to add a certain rule?
>
> Thanks for your ideas!
>
> Best regards.
> Nicolas
> --
> Freundliche Grüsse,
> Nicolas Odermatt
>
>
>
> ___
> 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] Docs: nova-manage network create FAILURE

[Diego Parrilla Santamaría]

Alexey,

Here goes a sample what we use in the distro:

FlatDHCP
./nova-manage network create service 10.0.0.0/24 1 256
--bridge=br100--bridge_interface=
bond1 --dns1=8.8.8.8 --dns2=8.8.4.4

VlanManager
./nova-manage network create service 10.0.0.0/24 1 256 --vlan=100
--bridge_interface=bond1 --dns1=8.8.8.8 --dns2=8.8.4.4

Keep in mind that FlatDHCP and VlanManager handle the tenants' networks
with different approach.

Cheers
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Mon, Feb 27, 2012 at 4:23 PM, Alexey Eromenko  wrote:

> --flat_interface (for flatdhcp mode)
> Doesn't work.
>
> Either the docs is wrong or the software.
> When I set "--flat_injected option", nova fails to work.
>
> root@nova-server1:~# nova-manage
> Usage: nova-manage [options]
>
> nova-manage: error: --flat_injected option does not take a value
>
> See:
> Docs: (compute) FlatDHCP disallows IP injection
> https://bugs.launchpad.net/openstack-manuals/+bug/941978
>
> Proposed fix:
> Remove "--flat_injected=False" altogether from FlatDHCP docs.
> Or it should work without options ?
> According to my understanding, only Flat mode has IP injection, while
> FlatDHCP does not.
>
> Is this correct ?
>
> On Mon, Feb 27, 2012 at 3:20 AM, Anne Gentle  wrote:
> > Good explanation, thanks Vish.
> >
> >
> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-flat-dhcp-networking.html
> > has the --flat_interace requirement, and
> >
> http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-vlan-networking.html
> > describes the --vlan_interface requirement.
> >
> > Thanks for asking Alexey. We can edit the page with the nova-manage
> > network create command also.
>
> Problem is:
>
> Networking described in Chapter: "Configuring Multiple Compute Nodes",
> which comes *after* Chapter: "Setting Up OpenStack Compute Environment
> on the Compute Node"
>
> So it fails.
>
> Moreover:
> "Configuring Multiple Compute Nodes" needs
> an example of what this looks like with real values entered.
>
> --
> -Alexey Eromenko "Technologov"
>
> ___
> 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] Announcing StackTach ...

[Diego Parrilla Santamaría]

Great job Sandy,

Correct me if I'm wrong, but you are using the events generated and
described in the SystemUsage blueprint (
http://wiki.openstack.org/SystemUsageData).

We are going to send a new blueprint (or I should say a part II of the
existing blueprint) to extend the current implementation of System Usage
notifications to cover more resources of Nova (volumes, floating ips, fixed
networks, tenants, images...). Sounds to me like a good fit.

We would like to contribute in Folsom developing these enhancements, and I
think your stackstach tool will help a lot.

Regards
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**




On Mon, Feb 20, 2012 at 9:15 PM, Sandy Walsh wrote:

> Hey!
>
> Last week I started on a little debugging tool for OpenStack based on
> AMQP events that I've been calling StackTach. It's really handy for
> watching the flow of an operation through the various parts of OpenStack.
>
> It consists of two parts:
>
> 1. The Worker.
>
> Sits somewhere on your OpenStack network. It listens to AMQP "monitor.*"
> notifications and sends them to the StackTach server.
>
> (I need this branch to land for it to work ... hint hint)
> https://review.openstack.org/#change,4194
>
> 2. The Web Interface
>
> Collects events via REST calls (poorman multi-tenant) and presents these
> events in a funky little web interface.
>
> You can play around with the UI here:
> http://darksecretsoftware.com/stacktach/1/
> (this is with data coming from my personal OpenStack Dev env)
>
> "What do I do?"
>
> Click on anything and you'll see the particulars in the Details window.
> Click on [+] to see the JSON for the event.
> "Hosts" shows the last 20 events that have a Host defined.
> "Instances" shows the last 20 events that have the Instance field
> populated.
> Hosts and Instances windows are resize-able.
> You may see duplication between both windows.
> Click on Time to see any events around that time (+/- 1 minute I think)
>
> "Where is the code?"
>
> The code is hosted below. There's LOTS of work to do to make it ready
> for prime-time ... but please, contribute.
>
> https://github.com/rackspace/stacktach
>
> "How do I install it?"
>
> I need to make this process cleaner. Right know you need to know how to
> create a Django Project and stick StackTach in there.
>
> Look forward to the feedback.
>
> Cheers,
> Sandy
>
>
> ___
> 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] Howto Nova setup with HA?

[Diego Parrilla Santamaría]

This is the kind of flame war I love... ;-)

if you think the HA challenges in Openstack Nova are at MySQL and Rabbit
level, you are not putting the focus on the right components. The biggest
HA  (and scalability) challenges in Nova are in the networking side. There
are a lot of companies tackling the networking challenges of Nova
(BigSwitch, Nicira, Cisco, etc...), and I would like to see how they evolve
in the future and how they will address this problem. Right now, only
promises.

Fight!
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Tue, Feb 21, 2012 at 1:04 PM, i3D.net - Tristan van Bokkem <
tristanvanbok...@i3d.nl> wrote:

> **
> Hi Darren,
>
> No, I am not looking at a performance increasment at this moment. Just
> trying to make the different components Nova is build on redundant. Of
> course a master/master setup of mysql / rabbitmq with a floating IP will
> probably work but it bugs me that Nova is not really build with flexibility
> of it components in mind.
>
> I understand it is impossible to cover every scenario and you can make
> things redundant into the infinitive but why doesn't have Nova any of this
> build in? Why do I need to setup a Virtual IP/floating IP where Nova simple
> could accept multiple locations and failover if the first location fails.
> Or even round-robin to distribute the load. All I am doing now is yet add
> another component that can possibly fail as well.
>
>
> Best regards,
>
> Tristan van Bokkem
> Datacenter Operations
>
> Contact:
> E-mail Personal: tristanvanbok...@i3d.net
> E-mail Support: i...@i3d.net
> E-mail NOC: n...@i3d.net
> Website: http://www.i3d.net Office:
> Interactive 3D B.V.
> Meent 93b
> 3011 JG Rotterdam
> The Netherlands
>
> Visit www.smartdc.net – SmartDC is our in-house 36,000 sq. ft. datacenter
> in Rotterdam, The Netherlands. High density hosting – multiple fiber
> carriers in-house – Level3 PoP.
>
> Interactive 3D (i3D.net) is a company registered in The Netherlands at
> Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01.
> Interactive 3D (i3D.net) is CDSA certified on content protection and
> security. We are ranked in the Deloitte Technology Fast 50 as one of the
> fastest growing technology companies.
>
> --
> *From:* Darren Birkett [mailto:darren.birk...@gmail.com]
> *To:* i3D.net - Tristan van Bokkem [mailto:tristanvanbok...@i3d.nl]
> *Cc:* Florian Haas [mailto:flor...@hastexo.com],
> openstack@lists.launchpad.net
> *Sent:* Tue, 21 Feb 2012 12:51:11 +0100
>
> *Subject:* Re: [Openstack] Howto Nova setup with HA?
>
> Surely it depends what you want out of it? If just pure high
> availability (ie ability to continue functioning when primary node
> goes down), then doesn't a master/master with floating IP fit the
> bill?
>
> It sounds like what you're after is better performance/throughput
> rather than HA - the ability to write to multiple masters at the same
> time. Even here if nova *was* able to hit multiple databases, a
> master/master setup isn't going to suit, as each write to one master
> still needs to be replicated to the other so throughput is going to be
> the same. You'd then need to look to something like a native mysql
> cluster to get actual increased throughput.
>
> Darren
>
> On 21 February 2012 11:34, i3D.net - Tristan van Bokkem
>
>  wrote:
> > Ho Florian,
> >
> > I respect your opinion of course and I am not here to start a fight.
> Point
> > is, how I understand it Nova really isn't very flexible on High
> Availability
> > terms. I have now a master/master mysql setup with a Virtual IP working
> just
> > to work around the shortcomings Nova imo introduces. This same story goes
> > for RabbitMQ, I need to setup RabbitMQ in HA (which is fine) but I need
> to
> > setup a Virtual IP for it as well just so Nova can correctly connect to
> it.
> > Without the VIP the hole point of setting it up in a cluster is useless
> as
> > you still will point nova to one single host.
> >
> > It shouldn't be that hard to make Nova listen to multiple mysql addresses
> > and rabbitmq hosts in a cluster?
> >
> >
> > Best regards,
> >
> > Tristan van Bokkem
> > Datacenter Operations
> >
> > Contact:
> > E-mail Personal: tristanvanbok...@i3d.net
> > E-mail Support: i...@i3d.net
> > E-mail NOC: n...@i3d.net
> > Website: http://www.i3d.net Office:
> > Interactive 3D B.V.
> > Meent 93b
> > 3011 JG Rotterdam
> > The 

Re: [Openstack] First batch of invites to the Folsom Design Summit

[Diego Parrilla Santamaría]

Stefano,

what about people not in the authors file but proposing new or upgraded
blueprints for Folsom?

Ciao
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Mon, Feb 20, 2012 at 3:27 AM, Stefano Maffulli wrote:

> Dear all,
>
> we have just sent out the first batch of invites to the Folsom Design
> Summit. If your email is in the Authors file of any of OpenStack
> repositories (or in the review system), you should have received an
> invite to register to the summit. If you haven't, check your spam
> filters and let me know.
>
> All PTLs have received also an extra set of invite codes so that they
> can invite more people that, at their discretion, they feel that they
> should attend to the summit.
>
> The rationale for sending private invitations initially to existing
> developers is that space is limited, so in the spirit of ensuring
> critical contributors can attend, we have started the process by sending
> invites to peoples whose names appears in the authors file. To get
> contact info we cross checked this with the review system.
>
> Depending on how many seats we have left after this first batch, we may
> send another batch of invites, or open the registration for anybody
> interested. We can discuss how to proceed at the next PPB on Tuesday.
>
> Let me know if this is not clear.
> Regards,
> stef
>
>
> ___
> 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] Fwd: NFS for nova-volume

[Diego Parrilla Santamaría]

Hi Salman,

you can checkout the directory in our stable/diablo branch in our repos in
GitHub:

https://github.com/StackOps/nova/commits/stable/diablo

You need to configure it as follows:

- NovaVolume nodes must have access to qemu-img executable. Otherwise it
won't be able to create the nodes.
- Share a filesystem for the volumes, for example /var/lib/nova/volumes
- in the configuration file of NovaVolume, you need to enter this flags:
flags.DEFINE_string('volumes_path', '/var/lib/nova/volumes', 'shared
directory for the volumes virtual disks')
flags.DEFINE_string('volumes_path_testfile', '%s/testfile' %
FLAGS.volumes_path, 'Test file to check if qemu-img works')
flags.DEFINE_string('volume_driver', 'nova.volume.nas.QEMUDriver', 'QEMU
Volumes driver')

We have an experimental release in our 0.4 version of the StackOps Distro
and in our Enterprise Distro, hopefully to release in the coming weeks.
Cheers
Diego
-- 
 Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.





2012/2/14 Diego Parrilla Santamaría 

> We have developed a QEMUDriver for stable/diablo, sadly the essex build is
> still broken. We are a bit overwhelmed, and we would like to contribute it
> in the future (gue rivero will help us with Gerrit).
>
> Still, if anybody wants to test it in stable/diablo, we are more than open
> to help him to use it.
>
> Cheers
> Diego
> --
> Diego Parrilla
> <http://www.stackops.com/>*CEO*
> *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * <http://www.stackops.com/>
> **
>
>
>
> On Tue, Feb 14, 2012 at 2:21 AM, Salman A Baset wrote:
>
>>  Hello folks,
>>
>> I was wondering if anyone has tried setting up nova-volume on NFS backend
>> without making any changes to nova-volume code?
>>
>> There is a Xen Storage Manager Volume driver that can support NFS, but I
>> am looking for a non-Xen solution.
>> http://nova.openstack.org/devref/xensmvolume.html
>>
>> Thanks.
>> Salman
>>
>> ___
>> 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] NFS for nova-volume

[Diego Parrilla Santamaría]

We have developed a QEMUDriver for stable/diablo, sadly the essex build is
still broken. We are a bit overwhelmed, and we would like to contribute it
in the future (gue rivero will help us with Gerrit).

Still, if anybody wants to test it in stable/diablo, we are more than open
to help him to use it.

Cheers
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Tue, Feb 14, 2012 at 2:21 AM, Salman A Baset  wrote:

>  Hello folks,
>
> I was wondering if anyone has tried setting up nova-volume on NFS backend
> without making any changes to nova-volume code?
>
> There is a Xen Storage Manager Volume driver that can support NFS, but I
> am looking for a non-Xen solution.
> http://nova.openstack.org/devref/xensmvolume.html
>
> Thanks.
> Salman
>
> ___
> 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 on i8ln?

[Diego Parrilla Santamaría]

Joshua, most of non-english speaking developers I know try to use english
for class names, methods, fields, constants... English is the 'lingua
franca' for code, so even developers with bad english level like me try to
use english all the time... so internationalized logging messages do not
make sense from my perspective. And sometimes translations are awful, or
even hilarious.

So +1 for english only logging messages in the code.

Cheers
Diego

P.D.: I know this is the kind of topic everybody has an opinion, so I hope
nobody feels attacked ;-)
-- 
Diego Parrilla
 <http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**



On Mon, Feb 13, 2012 at 9:50 PM, Joshua Harlow wrote:

>  Hi all,
>
> I was just wondering if I could get clarification on something I never
> understood related to i8ln.
>
> In nova HACKING.rst there is a line that mentions how log messages should
> be using gettext for i8ln.
>
> Is it common in other companies to attempt to internationalize log
> messages?
>
> I’ve seen this throughout the different openstack code and never quite
> understood why.
>
> I can understand horizon being internationalized, but
> debugging/error/warning (logging) messages? Isn’t that meant to be read by
> a developer, who will most likely understand english (to some degree).
>
> ??
>
> -Josh
>
>
>
> ___
> 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] Any block storage folks interested in getting together?

[Diego Parrilla]

Sounds great. We will try to join the meeting.

Enviado desde mi iPad

El 13/02/2012, a las 19:06, John Griffith  
escribió:

> There's been a lot of new work going on specific to Nova Volumes the
> past month or so.  I was thinking that it's been a long time since
> we've had a Nova-Volume team meeting and thought I'd see if there was
> any interest in trying to get together next week?  I'm open to
> suggestions regarding time slots but thought I'd propose our old slot,
> Thursday Feb 23, 18:00 - 19:00 UTC.
> 
> Here's a proposed agenda:
> 
>* Quick summary of new blueprints you have submitted and completed
> (or targeting for completion) in Essex
>* Any place folks might need some help with items they've targeted
> for Essex (see if we have any volunteers to help out if needed)
>* Any updates regarding BSaaS
>* Gauge interest in resurrecting a standing meeting, perhaps every 2 weeks?
> 
> If you have specific items that you'd be interested in
> sharing/discussing let me know.
> 
> Thanks,
> 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

___
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] libvirt + kvm problem on ubuntu 10.04.3

[Diego Parrilla Santamaría]

Hi Roman,

our StackOps Distro is based in 10.04 and we had to modify some packages to
make  Diablo work with kvm: we changed qemu-kvm 0.12 to 0.14:

- qemu-common_0.14.0 and
- qemu-kvm_0.14.0.

Don't know if it can help, but you can give a try...

Cheers
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.




On Thu, Feb 9, 2012 at 1:59 PM, Roman Bogorodskiy wrote:

> Hi,
>
> I'm facing a strange problem with libvirt + kvm on Ubuntu 10.04.3.
>
> I have all-in-one installation of Essex-2. When I start an instance
> using 'nova boot', it shows its status as ACTIVE, but when I connect
> using vnc (by issuing 'vncdisplay' command in virsh for that instance),
> I can see it doesn't even boot and shows
>
> 'No bootable device' error.
>
> Here's the output of 'virsh dumpxml' for that instance and also
> libvirt's log file:
>
> http://dpaste.de/VeFeq/
>
> I also have a VM I spawned manually (i.e. not through on this box) and
> it works fine. Here's its log:
>
> http://dpaste.de/cp4C1/
>
> The only major difference I can see is that it's using 'boot=on' for
> drive. It's also not using kernel and initrd, but I've tried images with
> out it with the same result.
>
> I've also been experimenting with running kvm manually and found a
> reproducible crash:
>
> root@host:/var/log/libvirt/qemu# LC_ALL=C
> PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
> QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp
> 1,sockets=1,cores=1,threads=1 -name instance-006d -uuid
> 0ce3afdc-be2f-4079-d106-e70b287f9e26 -nodefaults -chardev
>
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-006d.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=readline -rtc base=utc -boot c
> -kernel /var/lib/nova/instances/instance-006d/kernel -initrd
> /var/lib/nova/instances/instance-006d/ramdisk -append root=/dev/vda
> -drive
>
> file=/var/lib/nova/instances/instance-006d/disk,if=none,id=drive-virtio-disk0,format=qcow2,boot=on
> -device
> virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
> -chardev
>
> file,id=charserial0,path=/var/lib/nova/instances/instance-006d/console.log
> -device isa-serial,chardev=charserial0,id=serial0 -chardev
> pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1
> -usb -vnc 0.0.0.0:2 -k en-us -no-kvm
> char device redirected to /dev/pts/20
> Segmentation fault
> root@host:/var/log/lib

[Openstack] Blueprint "implementation of a file based volume driver"

[Diego Parrilla Santamaría]

Hi all,

we have implemented some features in nova that can match to this blueprint:

https://blueprints.launchpad.net/nova/+spec/filedriver

We are more than happy to contribute the code to the community for Folsom
(It works in Diablo and Essex, but we think it's too late for Essex). So
anybody interested in helping us is more than welcomed. My biggest concerns
comes with the approval process through Gerrit (scary...).

Regards
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este  mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] What's the web server used in the Nova API server?

[Diego Parrilla Santamaría]

Hi Michael,

we deploy with an Apache + mod_proxy in front of all the nova APIs
processes. It works reasonably well. For Horizon we use Apache + WSGI mod
(well... everybody knows Horizon is a different beast...).

Tomcat is a different beast, for JVM stuff, you know. Openstack is python.

Cheers
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.




On Mon, Jan 16, 2012 at 1:41 PM, Michael Basnight wrote:

> Just curious, whats the reason we went with rolling our own instead of
> using something like nginx/apache2/etc w/ mod_wsgi?
>
> On Jan 16, 2012, at 2:14 AM, Thierry Carrez wrote:
>
> > Joe Smithian wrote:
> >> I browsed the openStack documentation but couldn't find information
> >> about the Nova API server.
> >> What's the web server used in the Nova API server?
> >> Can we use a different web server  such as Apache or Tomcat?
> >>
> >> I'd appreciate your comments.
> >
> > Nova uses Python eventlet WSGI servers.
> > You can't directly use a different web server, though you can certainly
> > place Nova API servers behind some other server.
> >
> > --
> > 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
>
>
> ___
> 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] "F" release naming poll - Cast your vote !

[Diego Parrilla Santamaría]

Just listening Johnny Cash's  'Folsom Prison Blues'!

... so my vote goes to...

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
**




On Thu, Jan 12, 2012 at 10:34 AM, Thierry Carrez wrote:

> Fawnskin, Felton, Fillmore, Flournoy, Folsom, Fortuna, Fowler...
> How should the "F" version of OpenStack, due Fall 2012, be named ?
>
> Please participate to the F naming poll at:
> https://launchpad.net/~openstack/+poll/f-release-naming/+vote
>
> Pick your choice among the 28 options we have ! This is open to all
> members of the Launchpad OpenStack team (which is an open team).
>
> The poll closes next Tuesday, January 17, at 21:30 UTC.
> Cheers,
>
> --
> 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
>
___
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] Configure Rate limits on OS API

[Diego Parrilla Santamaría]

Wow! Didn't know about it. Really valuable information. I have been looking
for that information for ages.

Happy New Year folks,
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.




On Tue, Dec 27, 2011 at 9:33 PM, Nirmal Ranganathan wrote:

> You can configure those values thru the paste conf.
>
> [filter:ratelimit]
> paste.filter_factory =
> nova.api.openstack.limits:RateLimitingMiddleware.factory
> limits =("POST", "*", ".*", 10, MINUTE);("POST", "*/servers", "^/servers",
> 50, DAY);("PUT", "*", ".*", 10, MINUTE);("GET", "*changes-since*",
> ".*changes-since.*", 3, MINUTE);("DELETE", "*", ".*", 100, MINUTE)
>
>
> On Mon, Dec 19, 2011 at 1:28 PM, Day, Phil  wrote:
>
>> Hi Folks,
>>
>> ** **
>>
>> Is there a file that can be used to configure the API rate limits for the
>> OS API on a per user basis ?
>>
>> ** **
>>
>> I can see where the default values are set in the code, but it looks as
>> if there should be a less brutal configuration mechanism to go along with
>> this ?
>>
>> ** **
>>
>> Thanks
>>
>> Phil 
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Nirmal
> 
> http://rnirmal.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
>
>
___
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] Quantum OVS over StackOPS

[Diego Parrilla Santamaría]

Hi,

sounds like ovs-ofctl is not in the path.

BTW, we decided to wait for quantum support in essex, but please don't
hesitate to drop us an email and we will try to help you.

Cheers
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.





On Wed, Dec 21, 2011 at 11:35 AM, Alisson Soares Limeira Pontes <
apon...@cpqd.com.br> wrote:

> Hi everybody,
>
> I am configuring nova to work with Quantum.
> When aplying the configurations for the OVS plugin I face this error.
>
> root@nova-compute-1:~# python ovs_quantum_agent.py ovs_quantum_plugin.ini
>
> Traceback (most recent call last):
>   File "ovs_quantum_agent.py", line 297, in 
> plugin = OVSQuantumAgent(integ_br)
>   File "ovs_quantum_agent.py", line 175, in __init__
> self.setup_integration_br(integ_br)
>   File "ovs_quantum_agent.py", line 188, in setup_integration_br
> self.int_br.remove_all_flows()
>   File "ovs_quantum_agent.py", line 89, in remove_all_flows
> self.run_ofctl("del-flows", [])
>   File "ovs_quantum_agent.py", line 86, in run_ofctl
> return self.run_cmd(full_args)
>   File "ovs_quantum_agent.py", line 58, in run_cmd
> p = Popen(args, stdout=PIPE)
>   File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
> errread, errwrite)
>   File "/usr/lib/python2.6/subprocess.py", line 1139, in _execute_child
> raise child_exception
> OSError: [Errno 2] No such file or directory
>
> Anyone know why? The file /usr/lib/python2.6/subprocess.py does exists!
> All steps before this (according to the OVS README) went well.
> I am using Quantum 2012.1-e2-ubuntu2 and the StackOPS0.3.
>
>
> --
> Alisson Pontes
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
On Wed, Dec 21, 2011 at 11:35 AM, Alisson Soares Limeira Pontes <
apon...@cpqd.com.br> wrote:

> Hi everybody,
>
> I am configuring nova to work with Quantum.
> When aplying the configurations for the OVS plugin I face this error.
>
> root@nova-compute-1:~# python ovs_quantum_agent.py ovs_quantum_plugin.ini
>
> Traceback (most recent call last):
>   File "ovs_quantum_agent.py", line 297, in 
> plugin = OVSQuantumAgent(integ_br)
>   File "ovs_quantum_agent.py", line 175, in __init__
> self.setup_integration_br(integ_

Re: [Openstack] Newby question

[Diego Parrilla Santamaría]

Thank you for your nice words!

Dual configuration is the most common configuration we use: you only need
to be cautious about how to configure the different networks. Just some
hints:

1) Leave the management network as simple as possible.
2) The service network (the one that connects all the virtual machines and
nova-network) needs a dedicated NIC (or virtual NIC if you are deploying in
a virtual lab with VMware for example) and must be connected to the same
group of ports, all with a single VLAN statically assigned to these ports.
It's important that nova-network and the virtual machines can see each
other.
3) The public network (the one you will use for the floating IPs) cannot be
shared with the service network at all. It can be shared with the
management network, but normally you can't do real stuff. A good solution
is to have a dedicated NIC connected to internet and configured with a
public CIDR, or if you are in a corporate environment connect it to the
corporate network. Probably you will have to statically assign the port of
the switch to the VLAN of the corporate network.

To be honest, most of the complains about the distro has to do with
networking, and we can't do a lot about it. We normally try to explain that
the single node deployment is like installing a MySQL server for
development in 10 minutes -everybody can do it-, but configuring a MySQL
server for production highly available is hard. Dual and Multi node
deployments can be like deploying the production-ready MySQL: it's not a
10' tasks :-(

Regards
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.




2011/12/16 Alexandre Parenteau 

> Diego,
>
> Just one word: fantastic!
>
> I could install, configure, launch my first VM while sipping a coffee!
>
> I can't wait to try the dial-nodes, do I need only a second switch?
>
> Thanks so much for stackops, and thanks all for your quick answers!
>
> alex
>
>
> 2011/12/16 Diego Parrilla Santamaría 
>
>> Hi Alexandre,
>>
>> you can build a simple SingleNode in Flat Network mode with our StackOps
>> Distro: http://www.stackops.org
>>
>> Once you have installed and configured the Single Node, then you can go
>> to /etc/nova/nova-controller.conf and you can find the configuration
>> details.
>>
>> If you feel brave enough to try a multi node deployment, then the
>> Stackops Distro will create a specific nova-network configuration file in
>> /etc/nova/nova-network.conf
>>
>> Don't forget that starting from Diablo some network configuration stuff
>> must be performed dire

Re: [Openstack] Newby question

[Diego Parrilla Santamaría]

Hi Alexandre,

you can build a simple SingleNode in Flat Network mode with our StackOps
Distro: http://www.stackops.org

Once you have installed and configured the Single Node, then you can go to
/etc/nova/nova-controller.conf and you can find the configuration details.

If you feel brave enough to try a multi node deployment, then the Stackops
Distro will create a specific nova-network configuration file in
/etc/nova/nova-network.conf

Don't forget that starting from Diablo some network configuration stuff
must be performed directly with nova-manage command.

Enjoy!
Diego

-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.




On Fri, Dec 16, 2011 at 8:21 AM, Alexandre Parenteau
wrote:

> Hi,
>
> For my company, I'd like to set-up a nova-compute All-In-One node, to
> replace a eucalyptus cluster which is showing age.
>
> Unfortunately I'm not well versed in networking, and have trouble
> grasping the difference between the multiple network managers, but I
> think I would need a Flat mode in my case.
>
> I have a simple question: could someone please provide a functional
> euca.conf, that is using only one NIC, and the relative
> /etc/network/interfaces, for Ubuntu 11.10/Diablo?
>
> Help much appreciated!
>
> alex
>
> p.s.: as a side node, I tried everywhere  the web for an explanation
> of how 'nova-manage network' relates to the flags passed inside
> nova.conf.
>
> ___
> 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] Nexenta Driver proposal

[Diego Parrilla Santamaría]

Hi all,

we have modified the Solaris volume driver code to work with Nexenta Block
Storage. Actually, we have succesfully deployed solutions with Nexenta and
Nova already.

You can check the code here:

https://github.com/StackOps/nova/tree/stable/diablo

So, we are happy to collaborate on this.

Regards
Diego
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.



On Mon, Nov 14, 2011 at 12:31 PM, Yuriy Taraday  wrote:

> Hello.
>
> The Openstack block volume storage demands high reliability and management
> automation. This can be achieved with specialized storage solutions, but
> Openstack still lacks integration with this type of storage back-ends.
>
> We have created a blueprint<http://wiki.openstack.org/NexentaVolumeDriver>on 
> new volume driver for Nova that uses Nexenta appliance as storage.
> Driver is finished and working with Diablo version of Nova.
>
> We’re looking forward to any comments and suggestions. We hope our code
> can eventually be merged into master development branch with our support.
>
> Kind regards, Yuriy.
>
> ___
> 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] Patched euca-tools to work w/ keystone

[Diego Parrilla]

+1

BTW, the where are the backports committed? In the stable/diablo branch in 
github?

Enviado desde mi iPad

El 30/10/2011, a las 22:21, Leandro Reox  escribió:

> Thanks a lot Ziad, will be cool to ge it in the back ports.
> 
> Regards
> 
> On Fri, Oct 28, 2011 at 5:11 PM, Ziad Sawalha  
> wrote:
> I think this was it:
> https://github.com/openstack/keystone/commit/2bb474331d73e7c6d2a507cb097c50
> cfe65ad6b6
> 
> Will try to get it in the back ports.
> 
> Z
> 
> On 10/28/11 1:57 PM, "Razique Mahroua"  wrote:
> 
> >Hey,
> >I never found out, in fact I only recall some mails exchange on a mailing
> >list, basically, there are two lines to change into :
> >/usr/local/lib/python2.6/dist-packages/keystone-1.0-py2.6.egg/keystone/mid
> >dleware/ec2_token.py
> >
> >   # o = urlparse(FLAGS.keystone_ec1_url)
> >   o = urlparse(FLAGS.keystone_ec2_url)
> >
> >and :
> >   # token_id = result['auth']['token']['id']
> >   token_id = result['access']['token']['id']
> >
> >Regards,
> >Razique
> >
> >Le 28 oct. 2011 à 20:04, Leandro Reox a écrit :
> >
> >> Hi guys,
> >>
> >> Anyone got the link to download the patched euca tools that work with
> >>keystone auth tokens to query the nova api ?
> >>
> >> Regards
> >>
> >> Lean ___
> >> 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] OpenSTack Minimum Spec

[Diego Parrilla Santamaría]

Frans,

the single node configuration of the Stackops Distro can work in very modest
environments. A P4 and 1.5GB should be enough if you want to deploy m1.tiny
instances with QEMU. If you want to manage the deployment in a training lab
probably you should check the tool.

Cheers
Diego
-
-- 
Diego Parrilla
<http://www.stackops.com/>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com/>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.





On Fri, Oct 28, 2011 at 7:21 AM, Frans Thamura  wrote:

> hi all
>
> i am writing specification for polytechnics related for lab,
>
> the regulator said, 1 PC must be for 1 student
>
> and several polytechnics have limited budget
>
> can share all?
>
> i have Pentium 4, run in single node :) but i think multicore
> processor are better,
>
> so for play around i recommend i7, for server i recommend 2 core Xeon for
> lab.
>
>
> my plan
>
> 1 PC = 1 student
>
> we will create group, to make student can do multinode.
>
>
>
> --
> Frans Thamura (曽志胜)
> Chief of Advisory
> Meruvian.
> Integrated Hypermedia Java Solution Provider.
>
> Mobile: +628557888699
> Blog: http://blogs.mervpolis.com/roller/flatburger (id)
>
> FB: http://www.facebook.com/meruvian
> TW: http://www.twitter.com/meruvian / @meruvian
> Website: http://www.meruvian.org
>
> "We grow because we share the same belief."
>
> ___
> 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] any easy use tools for end user access swift ?

[Diego Parrilla Santamaría]

Try these:

http://cyberduck.ch/
http://www.gladinet.com/

Cheers
Diego

-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.



On Wed, Aug 10, 2011 at 9:13 AM, tianyi wang  wrote:

>  Hi all,
>
> For end user I think they will not want to use Linux shell command like
> this : st -A https://proxy:8080/auth/v1.0 -U system:root -K testpass
> upload myfiles test.txt
>
> for upload files into swift.
>
> Any easy use tools for this ?
>
> Thanks
>
> Alex
>
>
> ___
> 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] Dashboard newbie question

[Diego Parrilla Santamaría]

Hi Devin,

It seems you are now using the openstackx extensions in the dashboard, but
browsing the code it seems security groups (or public IP management in
anyway) is not yet implemented.

Am I right about it? If so, when do you think the dashboard will manage
them? Can we help in anyway?

Cheers
Diego

-
-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.


On Thu, Aug 4, 2011 at 7:54 PM, Devin Carlen  wrote:

> Hi Joshua,
>
> Dashboard is currently in pretty good shape but the latest nova code in
> trunk has a few issues.  I recommend using the Diablo-3 milestone release of
> Nova.  You should have better luck with that.
>
>
>
> On Aug 4, 2011, at 10:23 AM, Joshua Harlow wrote:
>
>  Hi all,
>
> I was just wondering if it is recommended or if anyone has been successful
> in getting the openstack dashboard up and running with the lastest nova
> code.
>
> I seem to be encountering some 400 http responses when say deploying from
> the dashboard.
>
> Is that just because the dashboard isn’t fully integrated yet?
>
> Thanks,
>
> Josh
> ___
> 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] Making Nova HA summit notes

[Diego Parrilla Santamaría]

Awesome Vish. I will give this network option a try!

Diego

-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.



On Thu, Jul 21, 2011 at 6:24 PM, Vishvananda Ishaya
wrote:

> We just recently merged a new HA networking option.  See details in my blog
> post here:
>
> http://unchainyourbrain.com/openstack/13-networking-in-nova
>
> <http://unchainyourbrain.com/openstack/13-networking-in-nova>Vish
>
> On Jul 20, 2011, at 10:04 PM, Mike Scherbakov wrote:
>
> Hi,
> Thank you for the work on making nova components HA.
>
> Did you have a chance to move further in this topic?
> I especially interested in making nova-network HA and looking for possible
> active-active implementations,
> so the downtime of the service would me minimal.
>
> Thank you,
>
> On Tue, May 3, 2011 at 1:22 PM, Edward Konetzko <
> konet...@quixoticagony.com> wrote:
>
>> I have attached the slides and Tushar Patil doc on making nova-network ha
>> along with the etherpad notes on the bottom.
>>
>>
>> I hope to follow this email up later on in the week with plans for a full
>> reference document based on Cacti.  Thanks for everyone’s participation at
>> the Summit.
>>
>> Thanks
>> Edward Konetzko
>>
>> Etherpad notes
>>
>>
>> This Etherpad is for the
>> Discussion on Design & Software Considerations for Making Nova HA/Fault
>> Tolerant
>> Please put ideas or comments in the appropriate sections
>>
>>
>> Database
>> - Does zones alleviate the need for HAing the DB?
>>
>>
>>
>> RabbitMQ
>> For comparison http://wiki.secondlife.com/**
>> wiki/Message_Queue_Evaluation_**Notes<http://wiki.secondlife.com/wiki/Message_Queue_Evaluation_Notes>
>> - Need to update managers to create persistant queues and messages
>> - XMPP an alternate?
>> Talk to RabbitMQ devs about
>> - Long term can we use Burrow?
>>
>>
>> Nova-Network
>> NTT Data documentation mailed to openstack list for their heartbeat POC
>> tests
>> Are there issues running multiple network nodes and assigning the same IP
>> to mutlple instances?
>> How about VRRP protocol?
>>   --> we (NTT) are planning to evaluate VRRP using keepalived or some
>> other software. Does anyone knows suitable software?
>>
>>
>> Nova-scheduler
>> Vish said you can run more then one
>> - Yeah with zones and how the scheduler is structured now, it can
>>
>>
>> Nova-api
>> Poss

Re: [Openstack] Index out of range during nova-manage

[Diego Parrilla Santamaría]

mmm give our distro a try: http://www.stackops.org

But I copied the parameters from Cactus-based running system.

Cheers
Diego

2011/7/20 Shehjar Tikoo 

> Thanks. It still runs into the Index out of range error. Are there any
> configurables we could look at to debug further?
>
> -Shehjar
>
> Diego Parrilla Santamaría wrote:
>
>> it seems fixed range and network size they don't match.
>>
>> It seems you are running a small environment. Try with this parameters:
>>
>> /usr/bin/nova-manage network create 10.0.0.0/ <http://10.0.0.0/24>8 1 255
>>
>> and
>>
>> --fixed_range=10.0.0.0/ <http://10.0.0.0/12>8
>> --network_size=64
>>
>> Diego
>>
>>
>> On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo > shehj...@gluster.com>> wrote:
>>
>>Hi all, I am running into a "Command failed, please check log for
>>more info" error on running the following command:
>>
>>/usr/bin/nova-manage network create 10.0.0.0/24 <http://10.0.0.0/24>
>>
>>1 255
>>
>>/var/log/nova/nova-manage.log contains the output at
>>http://pastebin.com/HP85LKQE
>>
>>The nova.conf contains;
>>--dhcpbridge_flagfile=/etc/__**nova/nova.conf
>>--dhcpbridge=/usr/bin/nova-__**dhcpbridge
>>--logdir=/var/log/nova
>>--state_path=/var/lib/nova
>>--lock_path=/var/lock/nova
>>--verbose
>>--s3_host=192.168.1.154
>>--rabbit_host=192.168.1.154
>>--cc_host=192.168.1.154
>>--ec2_url=http://192.168.1.__**154:8773/services/Cloud
>>
>> <http://192.168.1.154:8773/**services/Cloud<http://192.168.1.154:8773/services/Cloud>
>> >
>>--fixed_range=10.0.0.0/12 <http://10.0.0.0/12>
>>
>>--network_size=8
>>--FAKE_subdomain=ec2
>>--routing_source_ip=192.168.1.**__154
>>--verbose
>>
>> --sql_connection=mysql://root:**__gluster123@192.168.1.154/**nova<http://root:__gluster123@192.168.1.154/nova>
>>
>> <http://root:gluster123@192.**168.1.154/nova<http://root:gluster123@192.168.1.154/nova>
>> >
>>
>>--network_manager=nova.__**network.manager.FlatManager
>>
>>
>>I am simply following the instructions in Section 3.5.2 in the
>>Cactus compute admin guide. Appreciate any help here. Thanks.
>>-Shehjar
>>
>>__**___
>>Mailing list: 
>> https://launchpad.net/~__**openstack<https://launchpad.net/~__openstack>
>><https://launchpad.net/~**openstack <https://launchpad.net/~openstack>
>> >
>>Post to : openstack@lists.launchpad.net
>><mailto:openstack@lists.**launchpad.net
>> >
>>
>>Unsubscribe : 
>> https://launchpad.net/~__**openstack<https://launchpad.net/~__openstack>
>><https://launchpad.net/~**openstack <https://launchpad.net/~openstack>
>> >
>>More help   : 
>> https://help.launchpad.net/__**ListHelp<https://help.launchpad.net/__ListHelp>
>>
>> <https://help.launchpad.net/**ListHelp<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-operators] FLAG --start_guests_on_host_boot=true

[Diego Parrilla Santamaría]

We are testing this flag for the 0.3 version of the Stackops Distro. Our
goal is to restart the VMs in a different compute-node if a server fails
automatically.


On Wed, Jul 20, 2011 at 1:08 AM, Vishvananda Ishaya
wrote:

> Hmm, this flag needs to be set when the instance is created, so it will
> only work for new instances.
>
> I'm not sure if this flag was in cactus or not.
>
> As a workaround, you can manually turn on autostart for the domains using
> virsh on the compute host
> virsh autostart instance-0001 (for example)
>
> Vish
>
> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>
> HI all,
>
> Cant find any reference about this flag on the openstack docs 
> --start_guests_on_host_boot=true,
> is really available ? If so, even if i setted up on hthe compute nova.conf,
> doesnt restart instances at node reboot Using Cactus by now Any clues ?
> Regards ___
> 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-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
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-operators] FLAG --start_guests_on_host_boot=true

[Diego Parrilla Santamaría]

Yes, 0.3 will be based in Diablo.

2011/7/20 Leandro Reox 

> Diego,
>
> Thats the "rescue" option from Diablo, you can use this instead if youre
> planing to do it with cactus :
> https://github.com/Mirantis/openstack-utils/blob/master/nova-compute
>
> Regards
>
>
> 2011/7/20 Diego Parrilla Santamaría 
>
>> We are testing this flag for the 0.3 version of the Stackops Distro. Our
>> goal is to restart the VMs in a different compute-node if a server fails
>> automatically.
>>
>>
>> On Wed, Jul 20, 2011 at 1:08 AM, Vishvananda Ishaya <
>> vishvana...@gmail.com> wrote:
>>
>>> Hmm, this flag needs to be set when the instance is created, so it will
>>> only work for new instances.
>>>
>>> I'm not sure if this flag was in cactus or not.
>>>
>>> As a workaround, you can manually turn on autostart for the domains using
>>> virsh on the compute host
>>> virsh autostart instance-0001 (for example)
>>>
>>> Vish
>>>
>>> On Jul 15, 2011, at 7:13 AM, Leandro Reox wrote:
>>>
>>> HI all,
>>>
>>> Cant find any reference about this flag on the openstack docs 
>>> --start_guests_on_host_boot=true,
>>> is really available ? If so, even if i setted up on hthe compute nova.conf,
>>> doesnt restart instances at node reboot Using Cactus by now Any clues ?
>>> Regards ___
>>> 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-operators mailing list
>>> openstack-operat...@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>
>
___
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] Index out of range during nova-manage

[Diego Parrilla Santamaría]

it seems fixed range and network size they don't match.

It seems you are running a small environment. Try with this parameters:

/usr/bin/nova-manage network create 10.0.0.0/ 8 1 255

and

--fixed_range=10.0.0.0/ 8
--network_size=64

Diego

On Wed, Jul 20, 2011 at 3:00 PM, Shehjar Tikoo  wrote:

> Hi all, I am running into a "Command failed, please check log for more
> info" error on running the following command:
>
> /usr/bin/nova-manage network create 10.0.0.0/24 1 255
>
> /var/log/nova/nova-manage.log contains the output at
> http://pastebin.com/HP85LKQE
>
> The nova.conf contains;
> --dhcpbridge_flagfile=/etc/**nova/nova.conf
> --dhcpbridge=/usr/bin/nova-**dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --verbose
> --s3_host=192.168.1.154
> --rabbit_host=192.168.1.154
> --cc_host=192.168.1.154
> --ec2_url=http://192.168.1.**154:8773/services/Cloud
> --fixed_range=10.0.0.0/12
> --network_size=8
> --FAKE_subdomain=ec2
> --routing_source_ip=192.168.1.**154
> --verbose
> --sql_connection=mysql://root:**gluster123@192.168.1.154/nova
> --network_manager=nova.**network.manager.FlatManager
>
>
> I am simply following the instructions in Section 3.5.2 in the Cactus
> compute admin guide. Appreciate any help here. Thanks.
> -Shehjar
>
> __**_
> 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] Can I use StackOps Smart Installer without public internet access

[Diego Parrilla Santamaría]

Wow! I cannot explain it better! Gracias Leandro!

Basically, your nova nodes don't need internet access, but your browser
yes.
Diego

On Tue, Jul 5, 2011 at 2:38 PM, Leandro Reox  wrote:

> In the Stackops official doc says :
>
> *"Internet access in the Openstack Nodes*
>
> You don't need internet access in the installed Openstack nodes. The Smart
> Installer does not connect directly to the Stackops Agent. It uses the
> browser as a man in the middle to connect to the agent. "
>
> So basically you need internet connection on the browser that is trying to
> setup the node, can be proxied without issues ( i tried that and works like
> charm)
>
> But if you dont have internet access at ALL on the machine from that you
> accessing the node for installation process, or proxied access you cannot
> run the Smart Installer
>
> Regards
> lele
>
> On Tue, Jul 5, 2011 at 12:20 AM, Chen, Yan-Qiu (Daniel,
> ES-Best-Shore-Services-China-SH)  wrote:
>
>> Hi all,
>>
>> I installed the openstack controller in a virtual machine, and try to
>> configure the controller by StackOps Smart Installer(through the
>> http://:). But I found I was redirected to
>> http://installer.stackops.org/entrypoint  with the machine
>> hardware/software information posted to that address. What if I do NOT have
>> public internet access? Or the customer doesn’t like his machine information
>> is posted to public area? Is there a way to use the StackOps Smart Installer
>> without public internet access?
>>
>> Thanks in advance!
>>
>> Daniel
>>
>> ___
>> 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 nodes install

[Diego Parrilla Santamaría]

If you are considering FlatDHCP instead of VLAN, may be our distro can help
you: http://www.stackops.org

Still, you can manually change a running Stackops deployment to VLAN. It's
not a daunting task for an environment like yours.

Diego

P.D.: Sorry for this rather 'bizdev mode' announcement.
-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.




On Fri, Jun 24, 2011 at 4:09 AM, tianyi wang  wrote:

> Hi All,
>
>   I have two PC with same hardware configuration(Intel processor with
> VT，4G RAM, 500G harddisk) and want to install Multiple nodes openstack
> cloud.
>
>   I use the PC-A as Cloud Controller，PC-B as Compute Node. The LAN
> current situation：GateWay：192.168.2.1，PC-A：192.192.2.207, PC-B:
> 192.168.2.206, IP address allocate use DHCP.
>
>   The OS I use ubuntu 10.10 server or ubuntu 11.04 server.
>
>   Which software/services need be installed in Cloud Controller？
> Which software/services need be installed in Compute Node？ And what's
> the steps/install process ?
>
>   I want to use VLAN mode，how to configuration the network？
>
>   I have already follow this document:
>
> http://docs.openstack.org/cactus/openstack-compute/admin/content/manual-ubuntu-installation.html
>  install by myself 2 weeks.
>
>   But still can not let it work! This document maybe miss some
> details information for beginner.
>
>   Any more document in detail ?
>
>
>   Thanks
>
>   Alex
>
> 6.24.2011
>
> ___
> 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] euca-bundle-instance error

[Diego Parrilla Santamaría]

Hi all,

we are testing the Cactus release of Openstack Nova and we tried to bundle a
Windows instance with 'euca-bundle-instance' as follows:

Client OS: Ubuntu Natty 64 bits
euca2ools and dependencies: what comes in Natty by default, main-31337
2009-04-04 (1.3.1, because 1.2 did not have euca-bundle-instance)
Windows image: 2008SR2 Datacenter Version 64 bit

The Nova deployment is based on 10.04 and Cactus (Stackops distro based).

When I try to execute:

root@i-113c:/home/ubuntu# euca-bundle-instance i-1136 -b bucket -p
acens -o ${EC2_ACCESS_KEY} -w ${EC2_SECRET_KEY}

I get this error:

EC2Connection instance has no attribute 'bundle_instance'

So I don't know if I'm doing something wrong or euca2ools does not support
instance bundling yet... Anybody can give me a hint? Is there another way to
bundle an image?

Regards
Diego

-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.
___
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] Problems with re-bundle

[Diego Parrilla Santamaría]

Hi all,

We can reproduce the problem in our environments with the images downloaded
from  http://uec-images.ubutu.com :-(

Diego
-- 
 Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta al
secreto profesional, cuya divulgación no está permitida por la ley. En caso
de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and Internet
do not guarantee the confidentiality, nor the completeness or proper
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does
not assume any liability for those circumstances. Should you not agree to
the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively for
the person to whom it is addressed and contains privileged and confidential
information protected from disclosure by law. If you are not the addressee
indicated in this message, you should immediately delete it and any
attachments and notify the sender by reply e-mail. In such case, you are
hereby notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by law.



On Tue, Jun 7, 2011 at 1:47 PM, Thierry Carrez wrote:

> Muhammad Atif wrote:
> > 1- Downloaded the ubuntu1010 image from openstack site as follows:
> >
> > wget
> http://c0179148.cdn1.cloudfiles.rackspacecloud.com/ubuntu1010-UEC-localuser-image.tar.gz
>
> Any chance you could reproduce with an official Ubuntu image (downloaded
> from http://uec-images.ubuntu.com/) and file a bug on Launchpad ? This
> looks like a guest issue and with official images we  can get help from
> Ubuntu cloud image developers if need be...
>
> --
> 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
>
___
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] DRBD storage for Openstack installations

[Diego Parrilla Santamaría]

Hi Oleg,

thank you very much for your post, it's really didactic. We are taking a
different approach for HA at storage level, but I have worked formerly with
DRBD and I think it's a very good choice.

I'm curious about how you have deployed nova-volume nodes in your
architecture. You don't specify if the two nodes of the DRBD cluster run one
or two instances of nova-volume. If you run one instance probably you have
implemented some kind of fault-tolerant active-passive service if the
nova-volume process fails in the active node, but I would like to know if
you can run an active-active two nova-volume instances on two different
physical nodes on top of the DRBD shared resource.

Regards
Diego

-- 
Diego Parrilla
<http://www.stackops.com>*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
* <http://www.stackops.com>



On Thu, May 26, 2011 at 1:29 PM, Oleg Gelbukh  wrote:

> Hi,
> We were researching Openstack for our private cloud, and want to share
> experience and get tips from community as we go on.
>
> We have settled on DRBD as shared storage platform for our installation.
> LVM is used over the drbd device to mange logical volumes. OCFS2 file system
> is created on one of volumes, mounted and set up as *image_path* and *
> instance_path* in the *nova.conf*, other space is reserved for storage
> volumes (managed by nova-volume).
>
> As a result, we have shared storage suitable for features such as live
> migration and snapshots. We also have some level of fault-tolerance, with
> DRBD I/O error handling, which automatically redirects I/O requests to peer
> node over network in case of primary node failure. We created 
> script<https://github.com/Mirantis/openstack-utils/blob/master/recovery_instance_by_id.py>for
>  bootstrapping lost VMs in two crash scenarios:
> * dom0 host restart/domU failure: restore VMs on the same host
> * dom0 host failure: restore VMs on peer node
> We are considering such pair of servers with shared storage as a basic
> block for the cloud structure.
>
> For whom it may interest, the details of DRBD installation are 
> here<http://mirantis.blogspot.com/2011/05/shared-storage-for-openstack-based-on.html>.
> I'll be glad to answer any questions and highly appreciate feedback on this.
>
> Oleg S. Gelbukh,
> Mirantis Inc.
> www.mirantis.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
>
>
___
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] PREROUTING 169.254.169.254 rule shoud not on Compute node.......

[Diego Parrilla Santamaría]

Hi,

this is an issue in our Multi-Node arquitecture of the Stackops
Openstack Nova Distro. We have not verified 100% yet if it fix the
issue, but I think Hugo has found the reason and the solution, so my
sincere kudos, Hugo.

We will release a maintenance release once we verify that the rules
works fine in our lab.

Regards
-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo
electrónico y las comunicaciones por medio de Internet no permiten
asegurar ni garantizar la confidencialidad de los mensajes
transmitidos, así como tampoco su integridad o su correcta recepción,
por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna
por tales circunstancias. Si no consintiese en la utilización del
correo electrónico o de las comunicaciones vía Internet le rogamos nos
lo comunique y ponga en nuestro conocimiento de manera inmediata. Este
mensaje va dirigido, de manera exclusiva, a su destinatario y contiene
información confidencial y sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. En caso de haber recibido
este mensaje por error, le rogamos que, de forma inmediata, nos lo
comunique mediante correo electrónico remitido a nuestra atención y
proceda a su eliminación, así como a la de cualquier documento adjunto
al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al
mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES
S.L. does not assume any liability for those circumstances. Should you
not agree to the use of e-mail or to communications via Internet, you
are kindly requested to notify us immediately. This message is
intended exclusively for the person to whom it is addressed and
contains privileged and confidential information protected from
disclosure by law. If you are not the addressee indicated in this
message, you should immediately delete it and any attachments and
notify the sender by reply e-mail. In such case, you are hereby
notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by
law.




On Wed, May 11, 2011 at 4:08 AM, 郭耀謙  wrote:
> Hello , guys
> There's a problem while separate instance's network and nova-management
> network.
> EX.
> Nova management network : 192.168.1.0/24  eth0
> Instance network               :  10.0.0.0/12      eth1 bridge to br100
> During cloud-setup :
> Instance try to retrieve metadata from 169.254.169.254.
> Instances(10.0.0.0/12) request 169.254.169.254 PREROUTING from
> gateway(nova-network).
> But If PREROUTING rule is already been set on nova-Compute node, instance
> request will be redirected on VM host instead of nova-network host.
> So If your topology is like A diadram from StackOps , Plz Check iptables
> rule on Compute nodes.
> -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT
> --to-destination 192.168.1.2:8773
> And del this rule , your instance will get metadata correctly
>
>
>
>
> ___
> 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] Design Summit Decisions

[Diego Parrilla Santamaría]

Vish,

I miss the 'Notifications and Statistics' session. May be some of the
guys there can correct me (Jay?) if I'm wrong but we talked about:

- Extend Nova with a a server-to-server web-hook-based
publish/subscribe protocol: PubSubHubBub.
- Define a message format to describe the notification events.

Regards
Diego
-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo
electrónico y las comunicaciones por medio de Internet no permiten
asegurar ni garantizar la confidencialidad de los mensajes
transmitidos, así como tampoco su integridad o su correcta recepción,
por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna
por tales circunstancias. Si no consintiese en la utilización del
correo electrónico o de las comunicaciones vía Internet le rogamos nos
lo comunique y ponga en nuestro conocimiento de manera inmediata. Este
mensaje va dirigido, de manera exclusiva, a su destinatario y contiene
información confidencial y sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. En caso de haber recibido
este mensaje por error, le rogamos que, de forma inmediata, nos lo
comunique mediante correo electrónico remitido a nuestra atención y
proceda a su eliminación, así como a la de cualquier documento adjunto
al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al
mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES
S.L. does not assume any liability for those circumstances. Should you
not agree to the use of e-mail or to communications via Internet, you
are kindly requested to notify us immediately. This message is
intended exclusively for the person to whom it is addressed and
contains privileged and confidential information protected from
disclosure by law. If you are not the addressee indicated in this
message, you should immediately delete it and any attachments and
notify the sender by reply e-mail. In such case, you are hereby
notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by
law.



On Tue, May 3, 2011 at 12:22 AM, Vishvananda Ishaya
 wrote:
> Hey Everyone,
> I thought it would be nice to give everyone an update of the decisions made
> during the Design Summit.  There are a lot of follow-on actions.  I'll be
> spending the next week trying to get everything missing into blueprints and
> targeted to milestones, so that there is a cohesive view of the features
> being worked on for the Diablo release.  There are still a number of tasks
> for Nova that need to be done but have no one assigned.  I will list them
> below, but I will also be sending out specific emails to get volunteers for
> individual topics.
> The information below is based on notes that I took during the various
> meetings.  I attempted to collect as many of the action items related to
> Nova as possible.  Unfortunately, I wasn't in all of the sessions, and I'm
> sure I missed a few things. If others have additions/changes, please feel
> free to contribute them.
> I will also be sending out a list of milestones and dates so everyone can
> attempt to coordinate their development cycles with the official Nova
> milestones.
> Vish
> Diablo Design Summit Notes and Actions (* represents blueprints that need to
> be made)
> Six-Month Release Cycle
> OpenStack will move to a six month release cycle
> Releases will adopt the NVIE model -- Separate QA branch with bugfixes only
> merged in
> Project PTLs responsible for creating and assigning a QA team to manage the
> QA branch for release
> Milestones
> Between the six-month releases, individual projects can manage their own
> cadence for releases
> Unless a project has a good reason to change, it should adopt the default of
> one month milestones
> Milestones are not supported releases, but should expose stable new
> functionality
> Milestones will be used to target features and help ease the
> project-management burden
> Shared Code and New Projects
> Volume and Network code will initially not be separated into separate
> projects
> DB and API for volume and network should be separated within NOVA (*)
> Clear high-level apis will be defined for these components so other projects
> can replace them
> Shared code will be moved into a subfolder in nova for a possible move into
&

Re: [Openstack] Discussion on October Design Summit Locations

[Diego Parrilla Santamaría]

East Coast in the US is much better for European attendes like us. An
international airport hub should help a lot too.

-
Diego


On Wed, May 4, 2011 at 4:52 PM, Stephen Spector
 wrote:
>  On 5/3/11 8:44 PM, "Devin Carlen"  wrote:
>
>
>>There was a lot of talk earlier about Seattle and there seemed to be a
>>fair amount of interest.
>>
>>Devin
>
> Devin:
>
> Seattle was discussed but I thought that we should go to the East Coast in
> the US as we did the West Coast last week. Several attendees from Europe
> liked this idea as it will reduce their travel. Of course, there is no way
> to make everyone happy with location so my thinking is to bounce around
> various parts of the country/globe as we continue to have these events in
> the coming years.
>
> Stephen Spector
>
>
>
> ___
> 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 writing lock files in /usr/lib/pymodules/python2.6

[Diego Parrilla Santamaría]

I have found some random issues if you don't set the lock_path to a
writeable directory in Cactus. Never saw any issue in Bexar. Hence, in
the new version of our distro the lock_path parameter is always set.

-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla



On Wed, Apr 27, 2011 at 4:40 AM, Thomas Goirand  wrote:
> Hi,
>
> I thought I was the only one, as using Debian, but it seems I'm not.
>
> Nova is trying to write in /usr/lib/pymodules/python2.6. It should not,
> as an admin can decide to mount /usr read only. Here's the output:
>
> http://paste.openstack.org/show/1253/
>
> Of course, doing:
>
> chown nova /usr/lib/pymodules/python2.6
>
> kinds of fixes it, but that should never happens. Lock files should be
> written somewhere in /var, probably in /var/lib/nova/locks in this case.
>
> Is this a known issue (I haven't see it in a launchpad bug)? Is that an
> issue in python-lockfile? And more importantly: how to fix?
>
> I saw, in utils.py, a "FLAGS.lock_path". Should I just add a
> --lock_path=/var/lib/nova/locks in /etc/nova/nova.conf? In this case,
> why isn't /var/lib/nova/locks the default, and how to change that
> default in the code so that by default it goes in /var?
>
> Thomas Goirand (zigo)
>
> ___
> 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] Summit Talk: Information session on Zones? Any interest?

[Diego Parrilla]

+1

Enviado desde mi iPad

El 14/04/2011, a las 18:07, Sandy Walsh  escribió:

> I've been getting a lot of questions about Zones lately. 
> 
> How much interest is there for an informational session on Zones and, I 
> guess, Distributed Scheduler and roadmap?
> 
> (pending an available slot at the summit ... things are filling up quickly I 
> gather)
> 
> -S
> 
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of the
> individual or entity to which this message is addressed, and unless otherwise
> expressly indicated, is confidential and privileged information of Rackspace.
> Any dissemination, distribution or copying of the enclosed material is 
> prohibited.
> If you receive this transmission in error, please notify us immediately by 
> e-mail
> at ab...@rackspace.com, and delete the original message.
> Your cooperation is appreciated.
> ___
> 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] Enhancements to Glance in Diablo? Input welcomed

[Diego Parrilla Santamaría]

Hi Jay,

some random thoughts:

1) OVF support. I know it's not exactly a disk image format, but
probably we could look deeper if it make sense to add OVF or not. And
if not, where does it fit in the overall architecture.
2) "Understand what is contained in the disk images". Is this a
prerequisite for a kind of image builder, for example? May be I don't
get it, what is the purpose of it?

my two cents,

Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla





On Tue, Apr 12, 2011 at 8:11 PM, Jay Pipes  wrote:
> Hey all,
>
> We're in the planning stages for Diablo now, working on putting
> together blueprints, which turn into sessions at the design summit.
>
> I know the Glance team is small and our project narrow in scope, but
> it would be great to get some feedback from the list about stuff you'd
> like to see included in Glance in the Diablo release.
>
> Some possible thoughts:
>
> * Authn/authz - This is a big one, but dependent on the overall
> discussion of federated auth going on in the Nova/Swift communities.
> Glance will merely follow suit with what Nova does most likely.
> * Image conversion. This actually already has a blueprint, but maybe
> good for a detailed discussion at the summit? See
> https://blueprints.launchpad.net/glance/+spec/image-file-conversion
> * Metrics - for instance, tracking operations performed (read/write,
> bytes out/in, ?) Would this even be useful?
> * Integration with more backend storage systems?
> * XML support in the API?
> * Having Glance "understand" what is contained in the disk images by
> inspecting them on upload?
> * A Glance dashboard app?
>
> Please feel free to expand on any of the above and add any suggestions
> you have on the future direction of Glance. Your input is truly
> appreciated.
>
> Cheers!
> jay
>
> ___
> 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] (no subject)

[Diego Parrilla Santamaría]

I think it's a great feature, considering the problems to scale a
shared storage like NFS.

I was wondering if some Service Provider out there is going to
implement a shared storage to take advantage of the new KVM live
migration features of Cactus.

-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo
electrónico y las comunicaciones por medio de Internet no permiten
asegurar ni garantizar la confidencialidad de los mensajes
transmitidos, así como tampoco su integridad o su correcta recepción,
por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna
por tales circunstancias. Si no consintiese en la utilización del
correo electrónico o de las comunicaciones vía Internet le rogamos nos
lo comunique y ponga en nuestro conocimiento de manera inmediata. Este
mensaje va dirigido, de manera exclusiva, a su destinatario y contiene
información confidencial y sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. En caso de haber recibido
este mensaje por error, le rogamos que, de forma inmediata, nos lo
comunique mediante correo electrónico remitido a nuestra atención y
proceda a su eliminación, así como a la de cualquier documento adjunto
al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al
mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES
S.L. does not assume any liability for those circumstances. Should you
not agree to the use of e-mail or to communications via Internet, you
are kindly requested to notify us immediately. This message is
intended exclusively for the person to whom it is addressed and
contains privileged and confidential information protected from
disclosure by law. If you are not the addressee indicated in this
message, you should immediately delete it and any attachments and
notify the sender by reply e-mail. In such case, you are hereby
notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by
law.






On Mon, Apr 11, 2011 at 7:41 AM, igoigo246  wrote:
> hi all
>
> KVM Block Migration is wonderful function.
>
> http://www.linux-kvm.com/content/qemu-kvm-012-adds-block-migration-feature
>
> this allow   that live migration do  without shared storage.
>
>
> When KVM Block migration Support ?
>
>
> Thanks for reading.
> --
> Hisashi Ikari
>
>
> ___
> 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 automate replication

[Diego Parrilla Santamaría]

On Mon, Apr 4, 2011 at 3:27 PM, Jay Pipes  wrote:
> Persistence != HA. What are we talking about here? Both? I'm not sure...

Agree. Replication has to do more with DR services than HA. I tried to
prioritize instances Highly Avalaible and persistent instances (two
different features) before DR.

>
> -jay
>
> On Mon, Apr 4, 2011 at 12:20 AM, Jacob Gardiner  
> wrote:
>> I think the lines are blurring slightly.
>> It's not the responsibility of the infrastructure layer to ensure that the
>> application layer self-heals after an unscheduled reboot.
>> I don't think that a HA feature should be left out because there are
>> applications that may not heal, The discussion of infrastructure choice sits
>> with the application administrator and not the infrastructure developer -
>> you guys.
>> The openstack team is making good ground, but there's a key 'cloud' function
>> missing and its HA.
>>
>> On 03/04/2011, at 6:59 PM, Diego Parrilla wrote:
>>
>> +1
>> Some people think Cloud means 'magic' and failed physical instances should
>> recover to the previous state. Most of the times this is not possible at app
>> level, and I wonder if desirable.
>> Still, Nova lacks of features like 'HA' instances and instances running on
>> remote block storage (like EBS backed instances in AWS).I think this is
>> basic for self-healing features needed for real DR.
>>
>> Enviado desde mi iPad
>> El 02/04/2011, a las 22:46, Jesse Andrews  escribió:
>>
>> What to do when an instance dies is application specific.
>>
>> Some applications may not care, autoscaling back to the proper size by
>> themselves. Other applications may need the resources to be returned in the
>> most recent state.
>>
>> Currently openstack requires the user to handle recovery.
>>
>> I expect there will be an option to mark a virtual machine as "HA" which
>> would attempt to relaunch on crashes. How exactly to implement it will
>> depend on the cloud requirements. If the instances are backed to a SAN or
>> distributed filesystem (like ceph) the VM can be relaunched with all state
>> that has been flushed to disk. On a cloud with local disk only, the
>> scheduled snapshotting could allow the vm to a recent state.
>>
>> Or HA could mean relaunch the image (ala autoscale)
>>
>> What use case are you thinking about?
>>
>> Jesse
>>
>> On Apr 2, 2011 1:33 PM, "Marek Denis"  wrote:
>>> Hello,
>>>
>>> I have been trying to find out some info about features OpenStack
>>> provide and still cannot figure out whether 'cloud features' are
>>> available by default. By 'cloud features' I mean proper handling
>>> situations where we have many instances running on many different
>>> hardware servers. Suddently one server (physically) goes down, something
>>> bad happened. How will the OpenStack as a cloud behave by default? Will
>>> it run all the lost instances on other hardware servers or this should
>>> be specifically configured or programmed? How about data replication?
>>> Users shouldn't notice anything, as all the instances are ran in the
>>> cloud. Is it available by default? I couldn't find any docs that would
>>> explain these topics in a detailed way. Thanks for your explanation.
>>> --
>>> regards
>>>
>>> M
>>>
>>>
>>> ___
>>> 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
>>
>> Jacob Gardiner
>> National Hosting Manager
>> E jgardi...@squiz.com.au
>> Squiz Pty. Ltd. A 92 Jarrett Street, Leichhardt NSW 2040
>> P +61 2 8507 9900 F +61 2 8507 9988 SUPPORT 13000 SQUIZ W www.squiz.com.au
>> AUSTRALIA UNITED KINGDOM NEW ZEALAND EUROPE UNITED STATES
>> SYDNEY MELBOURNE CANBERRA HOBART BRISBANE
>>
>> SUPPORTED OPEN SOURCE SOLUTIONS
>>
>> ___
>> 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 automate replication

[Diego Parrilla]

+1

Some people think Cloud means 'magic' and failed physical instances should 
recover to the previous state. Most of the times this is not possible at app 
level, and I wonder if desirable.

Still, Nova lacks of features like 'HA' instances and instances running on 
remote block storage (like EBS backed instances in AWS).I think this is basic 
for self-healing features needed for real DR.


Enviado desde mi iPad

El 02/04/2011, a las 22:46, Jesse Andrews  escribió:

> What to do when an instance dies is application specific.
> 
> Some applications may not care, autoscaling back to the proper size by 
> themselves. Other applications may need the resources to be returned in the 
> most recent state.
> 
> Currently openstack requires the user to handle recovery.
> 
> I expect there will be an option to mark a virtual machine as "HA" which 
> would attempt to relaunch on crashes. How exactly to implement it will depend 
> on the cloud requirements. If the instances are backed to a SAN or 
> distributed filesystem (like ceph) the VM can be relaunched with all state 
> that has been flushed to disk. On a cloud with local disk only, the scheduled 
> snapshotting could allow the vm to a recent state.
> 
> Or HA could mean relaunch the image (ala autoscale)
> 
> What use case are you thinking about?
> 
> Jesse
> 
> On Apr 2, 2011 1:33 PM, "Marek Denis"  wrote:
> > Hello,
> > 
> > I have been trying to find out some info about features OpenStack 
> > provide and still cannot figure out whether 'cloud features' are 
> > available by default. By 'cloud features' I mean proper handling 
> > situations where we have many instances running on many different 
> > hardware servers. Suddently one server (physically) goes down, something 
> > bad happened. How will the OpenStack as a cloud behave by default? Will 
> > it run all the lost instances on other hardware servers or this should 
> > be specifically configured or programmed? How about data replication? 
> > Users shouldn't notice anything, as all the instances are ran in the 
> > cloud. Is it available by default? I couldn't find any docs that would 
> > explain these topics in a detailed way. Thanks for your explanation.
> > -- 
> > regards
> > 
> > M
> > 
> > 
> > ___
> > 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] installing Nova in the Cloud

[Diego Parrilla Santamaría]

Hi Nelson,

we have successfully deployed a multinode installation of Nova with
our distro Stackops on a VMware ESXi 4.1. QEMU is the only available
emulator when running on top of a hypervisor.

I guess you can use our distro to deploy on any Cloud Provider that
allows you to upload an ISO image and install it on several virtual
machines. As far as I know you can install ISOs in Terremark vCloud
Express, and they use VMware as the hypervisor. We use FlatDHCP as the
network model.

You can download the distro from http://www.stackops.org

Let us know if it works,

-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo
electrónico y las comunicaciones por medio de Internet no permiten
asegurar ni garantizar la confidencialidad de los mensajes
transmitidos, así como tampoco su integridad o su correcta recepción,
por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna
por tales circunstancias. Si no consintiese en la utilización del
correo electrónico o de las comunicaciones vía Internet le rogamos nos
lo comunique y ponga en nuestro conocimiento de manera inmediata. Este
mensaje va dirigido, de manera exclusiva, a su destinatario y contiene
información confidencial y sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. En caso de haber recibido
este mensaje por error, le rogamos que, de forma inmediata, nos lo
comunique mediante correo electrónico remitido a nuestra atención y
proceda a su eliminación, así como a la de cualquier documento adjunto
al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al
mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES
S.L. does not assume any liability for those circumstances. Should you
not agree to the use of e-mail or to communications via Internet, you
are kindly requested to notify us immediately. This message is
intended exclusively for the person to whom it is addressed and
contains privileged and confidential information protected from
disclosure by law. If you are not the addressee indicated in this
message, you should immediately delete it and any attachments and
notify the sender by reply e-mail. In such case, you are hereby
notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by
law.



On Thu, Mar 31, 2011 at 6:57 PM, Nelson Nahum  wrote:
> I would like to install Open Stack Nova in few servers in the cloud.
>
> Is this possible? Which version?
>
> Any specific Cloud provider recommendations?
>
> Thanks,
> Nelson Nahum
> nel...@zadarastorage.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
>
>

___
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 Design Summit - Fall 2011 Location Request

[Diego Parrilla Santamaría]

+1 to Europe!

-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parri...@stackops.com | +34 649 94 43 29 |
skype:diegoparrilla

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo
electrónico y las comunicaciones por medio de Internet no permiten
asegurar ni garantizar la confidencialidad de los mensajes
transmitidos, así como tampoco su integridad o su correcta recepción,
por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna
por tales circunstancias. Si no consintiese en la utilización del
correo electrónico o de las comunicaciones vía Internet le rogamos nos
lo comunique y ponga en nuestro conocimiento de manera inmediata. Este
mensaje va dirigido, de manera exclusiva, a su destinatario y contiene
información confidencial y sujeta al secreto profesional, cuya
divulgación no está permitida por la ley. En caso de haber recibido
este mensaje por error, le rogamos que, de forma inmediata, nos lo
comunique mediante correo electrónico remitido a nuestra atención y
proceda a su eliminación, así como a la de cualquier documento adjunto
al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al
mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES
S.L. does not assume any liability for those circumstances. Should you
not agree to the use of e-mail or to communications via Internet, you
are kindly requested to notify us immediately. This message is
intended exclusively for the person to whom it is addressed and
contains privileged and confidential information protected from
disclosure by law. If you are not the addressee indicated in this
message, you should immediately delete it and any attachments and
notify the sender by reply e-mail. In such case, you are hereby
notified that any dissemination, distribution, copying or use of this
message or any attachments, for any purpose, is strictly prohibited by
law.


On Tue, Mar 29, 2011 at 6:04 PM, Josh Kearney  wrote:
> Europe would be nice.
>
> On Tue, Mar 29, 2011 at 10:52 AM, Stephen Spector
>  wrote:
>>
>> Developers:
>> I have started early planning on the next OpenStack Design Summit in early
>> October 2011 this year and would like to get some feedback on location
>> options. The current thinking is to just host a Design Summit event for 3
>> days without the associated Conference portion that we are doing next month
>> in Santa Clara. It is my intention to take this idea to the broader
>> community in the coming weeks but I need to gather some data from the
>> developers before I can put together a final proposal to the community,
>> Location – My goal is to host the 3-day event in a gateway city so
>> attendees from Asia, Europe, and the US can easily fly directly to this
>> destination. This leads me to look at cities like New York, Chicago, London,
>> Paris, Seoul, etc except these locations tend to be expensive for hotels and
>> facilities. Other global cities such as Houston, Amsterdam, Frankfort,
>> Seattle, Atlanta, Dallas are cheaper locations for the event. Thus, I am
>> looking to see what locations are of interest to the developers; also
>> remember weather in October as a factor.
>> Host – Having an event at a hotel is more expensive then finding a
>> corporate facility, university setting, or even co-locate with a conference.
>> I am open to any ideas you have about interesting facilities or events to
>> co-locate with as I want to ensure that we not only accomplish our goal of
>> setting the project's direction for the future releases but also provide an
>> excellent environment with top notch facilities.
>> Feel free to provide your thoughts directly to myself via email or respond
>> to this email should you wish a broader conversation. Thanks.
>> - - -
>> Stephen Spector, Rackspace
>> OpenStack Community Manager
>> stephen.spec...@openstack.org
>> OpenStack Blog | @opnstk_com_mgr
>> Office  +1 (512) 539-1162 | Mobile +1 (210) 415-0930
>> ___
>> 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
> Unsub

[Openstack] VlanManager and Public IPs configuration

[Diego Parrilla Santamaría]

Hi all,

I cannot find information about how to set up an environment with Public IPs
and VlanManager enabled. I have tested FlatManager but it does not fully
cover our needs in terms of network isolation.

Basically what I'm trying to do is:

a) Setup a Controller Node with nova-api, nova-scheduler, nova-objectstorage
and nova-manage tools. It connects to the management network.
b) Setup a Network Node with 3 NICs. NIC X connects to the management
network. NIC Y connects to the service network (VLANs with Private IP
addressing) and NIC Z connects to the public network.
c) Setup a bunch of Compute Nodes with 3 NICs. NIC X connects to the
management network. NIC Y connect to the service network and NIC Z connects
to the storage network.
d) Setup a Storage Node with 2 NICs. NIC X connects to the management
network and NIC Y connect to the storage network.

My problem is... I cannot find information about:
1) How to setup the Network Node to support this architecture. I guess I
have to configure the nova-network to listen on a public interface... but
how?
2) What euca- commands do I need to execute to configure a 'elastic IP'?
3) How do I populate the pool of 'Elastic IPs'?

I don't need a long response... a nova.conf file of a similar configuration
would be enough, plus the basic commands to assign elastic IPs.

Thanks in advance!
-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
___
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] Decoupling of Network and Compute services for the new Network Service design

[Diego Parrilla Santamaría]

I think we had this conversation before some weeks ago. From my perspective
I think networking services are normally not considered as first class
citizens of the 'Virtual Datacenter'. What Ishimoto-san describes is a
Virtual Switch. But networking services in the day-in day-out operations
include also DNS management, load balancers, firewalls, VPNs, netflow and
others. And this is the main reason to decouple all these services from the
Virtual Machine lifecycle: they are a lot of heterogenous network services
and some make sense tied to the VM but others make sense tied to the Virtual
Datacenter (let's call it the Openstack Project concept).

The scheduler should handle the network services tied to the VM, but most of
the network services are tied to a different kind of resource scheduler, the
Virtual Datacenter resources scheduler. This is the orchestrator we are
discussing in this thread.

So before adding new virtual resources I think we need some kind of new
Orchestrator/Resource scheduler that should handle dependencies between
resources (a netflow listener needs a virtual Port of a virtual Switch to be
allocated) and pluggable services. What I'm not sure about this kind of
orchestration components is if they implement fixed or dynamic workflows.
Fixed workflows reduce complexity a lot.

A long email and my poor english... hope you understand it!

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Wed, Feb 23, 2011 at 9:47 PM, John Purrier  wrote:

> And we are back to the discussion about orchestration... Given the
> flexibility of the OpenStack system and the goals of independently
> horizontally scaling services I think we will need to address this head on.
> #3 is the most difficult, but is also the right answer for the project as
> we
> look forward to adding functionality/services to the mix. This is also
> where
> we can make good use of asynchronous event publication interfaces within
> services to ensure maximum efficiency.
>
> John
>
> -Original Message-
> From: openstack-bounces+john=openstack@lists.launchpad.net
> [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On
> Behalf
> Of Vishvananda Ishaya
> Sent: Wednesday, February 23, 2011 12:27 PM
> To: Ishimoto, Ryu
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Decoupling of Network and Compute services for the
> new Network Service design
>
> Agreed that this is the right way to go.
>
> We need some sort of supervisor to tell the network to allocate the network
> before dispatching a message to compute.  I see three possibilities (from
> easiest to hardest):
>
> 1. Make the call in /nova/compute/api.py (this code runs on the api host)
> 2. Make the call in the scheduler (the scheduler then becomes sort of a
> supervisor to make sure all setup occurs for a vm to launch)
> 3. Create a separate compute supervisor that is responsible for managing
> the
> calls to different components
>
> The easiest seems to be 1, but unfortunately it forces us to wait for the
> network allocation to finish before returning to the user which i dislike.
>
> I think ultimately 3 is probably the best solution, but for now I suggest 2
> as a middle ground between easy and best.
>
> Vish
>
> On Feb 23, 2011, at 5:29 AM, Ishimoto, Ryu wrote:
>
> >
> > Hi everyone,
> >
> > I have been following the discussion regarding the new 'pluggable'
> network
> service design, and wanted to drop in my 2 cents ;-)
> >
> > Looking at the current implementation of Nova, there seems to be a very
> strong coupling between compute and network services.  That is, tasks that
> are done by the network service are executed at the time of VM
> instantiation, making the compute code dependent on the network service,
> and
> vice versa.  This dependency seems undesirable to me as it adds
> restrictions
> to implementing 'pluggable' network services, which can vary, with many
> ways
> to implement them.
> >
> > Would anyone be opposed to completely separating out the network service
> logic from compute?  I don't think it's too difficult to accomplish this,
> but to do so, it will require that the network service tasks, such as IP
> allocation, be executed by the user prior to instantiating the VM.
> >
> > In the new network design(from what I've read up so far), there are
> concepts of vNICs, and vPorts, where vNICs are network interfaces that are
> associated with the VMs, and vPorts are logical ports that vNICs are
> plugged
> into for network connectivity.  If we are to decouple network and compute
> services, the steps required for FlatManager networking service would look
> somethin

Re: [Openstack] documentation of flags, introducing of a naming convention for flags

[Diego Parrilla Santamaría]

I forgot to add something to my 'wishlist' ;-)

Changing the way we configure Nova should be a process announced in
advanced. One or two releases in advance, to give enough time to teams
doing deployments and upgrades of Nova to be prepared. Changes that
can impact in the upgrade of the product (database schema changes,
ldap schema changes, deprecated/new properties should be informed in
advance).

I understand this is very complicated... but this is the kind of
things that sysadmins love.

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Wed, Feb 23, 2011 at 9:44 AM, Thierry Carrez  wrote:
> Andy Smith wrote:
>> (4) I did some work on a sphinx plugin that was never finished to
>> automatically document the flags, I can put some effort into finishing
>> that if we want it. It basically added the docs for the flags per module
>> and could be expanded to generate a master list of flags document also.
>
> That sounds great !
>
> Ideally each flag would be a bit more documented in code (not just a
> short desc and a default value) and the plugin would pick those comments up.
>
> Then it can serve as a basis to write the flags chapter in the user
> documentation ("OpenStack manuals"). This one needs a bit more human
> editing (logical groupings of flags, explanation of several flags at the
> same time...) but would use the Sphinx-plugin-generated doc as raw material.
>
> --
> 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
>

___
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] documentation of flags, introducing of a naming convention for flags

[Diego Parrilla Santamaría]

I have counted 160 configuration parameters in Nova, and only about 15
are documented. This is clearly one of the areas of improvement in the
project.

I have been fighting with Nova Bexar in not-so-standard configurations
and deployments and believe me, I would appreciate more information
about what they do.

Something that took me a lot of time to figure out was what are
'common' flags for all the components in nova, and what are 'specific'
flags for each component. If you are setting up an environment with
specialized nodes
(compute,network,volume,api,objectstore,scheduler...) this is a must
if you want to have more than a couple of servers running Nova.

Diego
-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Tue, Feb 22, 2011 at 3:29 PM, Jay Pipes  wrote:
> 
> Just use optparse/argparse. paste.deploy handles configuration files
> already, which is where most "flags" should really be... gflags adds
> unneeded complexity for no real gains, IMHO. Swift and Glance do just
> fine without gflags, as do the vast majority of Python projects. As
> for documentation of program options, the most common practice in the
> open source world is to document configuration options in the example
> configuration files that ship with your project, and document command
> line options "inline" to show up in --help output.
> 
>
> On Tue, Feb 22, 2011 at 1:37 AM, Christian Berendt
>  wrote:
>> Hi.
>>
>> At the moment we're using a lot of flags spread all over the code.
>>
>> a) we should create a useful documentation including all flags
>>
>> b) we should introduce a naming convention for new flags and we should
>> rename existing flags
>>
>> example:
>>
>> all flags related to default values are starting with "default_", all
>> flags related to a path are starting with "path_".
>>
>> Looks like most of the flags have good names at the moment, but I think
>> we should write it down in the wiki or the developer documentation to
>> reduce the possibility of bad names in the future.
>>
>> c) if it's possible we should collect all flags in one file
>>
>> At the moment the flags are defined in the files where they are used. I
>> think it would be nice to have on file, for example nova/flags.py,
>> including all flags used all over the code.
>>
>> Bye, Christian.
>>
>> --
>> Christian Berendt
>> Linux / Unix Consultant & Developer
>> Tel.: +49-171-5542175
>> Mail: bere...@b1-systems.de
>>
>> B1 Systems GmbH
>> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>>
>> ___
>> 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] Pondering multi-tenant needs in nova.

[Diego Parrilla Santamaría]

Sandy, Devin,

this is structure we had in my former cloud platform to fit easily in
a LDAP. It also helped in metering.

Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Thu, Feb 3, 2011 at 9:29 PM, Sandy Walsh  wrote:
> Sounds very LDAP.
> Would it make sense to have a plug-in so we could mimic a pre-existing corp
> LDAP structure?
> -S
>
> 
> From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
> [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf
> of Devin Carlen [devin.car...@gmail.com]
> Sent: Thursday, February 03, 2011 4:02 PM
> To: Monsyne Dragon
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] Pondering multi-tenant needs in nova.
>
> We were just talking about this the other day.  We definitely need some kind
> of further hierarchy.  I think a typical kind of use case for multi-tenant
> could be something like:
> Enterprise contains Organizations
> Organizations contain Organizations and Projects
> Projects contain Instances, etc.
>
> In this structure enterprise is just a top level organization.  If we
> structure it this way it would make metering and billing pretty simple.
>
>
>
>
> On Feb 2, 2011, at 5:37 PM, Monsyne Dragon wrote:
>
> I am sorting out some possible implementations for the
> multi-tenant-accounting blueprint, and the related system-usage-records bp,
> and I just wanted to run this by anyone interested in such matters.
>
> Basically, for multitenant purposes we need to introduce the concept of an
> 'account' in nova, representing a customer,  that basically acts as a label
> for a group of resources (instances, etc), and for access control (i.e
> customer a cannot mess w/ customer b's stuff)
>
> There was some confusion on how best to implement this, in relation to
> nova's project concept.  Projects are kind of like what we want an account
> to be, but there are some associations (like one project per network) which
> are not valid for our flat networking setup.  I am kind of straw-polling on
> which is better here:
>
> The options are:
> 1) Create a new 'account' concept in nova,  with an account basically being
> a subgroup of a project (providers would use a single, default project, with
> additional projects added if needed for separate brands, or resellers, etc),
> add in access control per account as well as project, and make sure
> apis/auth specify account appropriately,  have some way for a default
> account to used (per project) so account doesn't get in the way for
> non-multitenant users.
>
> 2) having account == nova's "project", and changing the network
> associations, etc so projects can support our model (as well as current
> models).  Support for associating accounts (projects) together for
> resellers, etc would either be delegated outside of nova or added later
> (it's not a current requirement).
>
> In either case, accounts would be identified by name, which would  be an
> opaque string an outside system/person would assign, and could structure to
> their needs (ie. for associating accounts with common prefixes, etc)
>
> --
>
> --
>    -Monsyne Dragon
>    work: 210-312-4190
>    mobile    210-441-0965
>    google voice: 210-338-0336
>
>
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at ab...@rackspace.com, and delete the original message.
> Your cooperation is appreciated.
>
>
> ___
> 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] Pondering multi-tenant needs in nova.

[Diego Parrilla Santamaría]

Thanks Paul. Your explanation really helps. A vlan is a scarce
resource in cloud infraestructures and most of the people don't know
about it.

I asked about this topic in this thread because I see two different
approaches that colides. And can have a huge impact in the 'account'
entity.

The truth is that most of the datacenter professionals I have talked
about reject the Flat Network model and embrace the VLAN (or more than
one VLAN) per customer model because it is what they know and they
feel 'secured' using them. Openstack let us choose what model to use,
and this great and I think should not change. So, creating an account
entitty directly linked to the network model is dangerous because it
can limit this flexibility.

I know, I have not given any valid answer... but it's something to
consider due to the efforts to support a more complex network
management.

Cheers
Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




2011/2/3 Paul Voccio :
> Diego,
>
> Due to our networking topology, having a vlan per customer isn't really
> feasible. Most switches are limited at 4k or 8k or even 32k. With more
> customers than these switches can reasonably accommodate, having a single
> vlan per customer either limits the portability within a cloud or limits
> the scale at which you can build your cloud. Open vSwitch will alleviate
> some of this pain, but until we get it in XenServer, we're somewhat stuck
> on flat networking.
>
> Paul
>
> On 2/3/11 4:20 AM, "Diego Parrilla Santamaría"
>  wrote:
>
>>Hi Monsyne,
>>
>>it's a very interesting topic and I'm curious about the reason why you
>>are using the Flat Networking set up. From the conversations in other
>>threads it seems the Service Providers prefer different networking
>>approaches: VLAN oriented basically.
>>
>>Regards
>>Diego
>>
>>-
>>Diego Parrilla
>>nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
>>+34 649 94 43 29
>>
>>
>>
>>
>>On Thu, Feb 3, 2011 at 2:37 AM, Monsyne Dragon 
>>wrote:
>>> I am sorting out some possible implementations for the
>>> multi-tenant-accounting blueprint, and the related system-usage-records
>>>bp,
>>> and I just wanted to run this by anyone interested in such matters.
>>>
>>> Basically, for multitenant purposes we need to introduce the concept of
>>>an
>>> 'account' in nova, representing a customer,  that basically acts as a
>>>label
>>> for a group of resources (instances, etc), and for access control (i.e
>>> customer a cannot mess w/ customer b's stuff)
>>>
>>> There was some confusion on how best to implement this, in relation to
>>> nova's project concept.  Projects are kind of like what we want an
>>>account
>>> to be, but there are some associations (like one project per network)
>>>which
>>> are not valid for our flat networking setup.  I am kind of
>>>straw-polling on
>>> which is better here:
>>>
>>> The options are:
>>> 1) Create a new 'account' concept in nova,  with an account basically
>>>being
>>> a subgroup of a project (providers would use a single, default project,
>>>with
>>> additional projects added if needed for separate brands, or resellers,
>>>etc),
>>> add in access control per account as well as project, and make sure
>>> apis/auth specify account appropriately,  have some way for a default
>>> account to used (per project) so account doesn't get in the way for
>>> non-multitenant users.
>>>
>>> 2) having account == nova's "project", and changing the network
>>> associations, etc so projects can support our model (as well as current
>>> models).  Support for associating accounts (projects) together for
>>> resellers, etc would either be delegated outside of nova or added later
>>> (it's not a current requirement).
>>>
>>> In either case, accounts would be identified by name, which would  be an
>>> opaque string an outside system/person would assign, and could
>>>structure to
>>> their needs (ie. for associating accounts with common prefixes, etc)
>>>
>>> --
>>>
>>> --
>>>    -Monsyne Dragon
>>>    work:         210-312-4190
>>>    mobile        210-441-0965
>>>    google voice: 210-338-0336
>>>
>>>
>>>
>>> Confidentiality Notice: This e-mail message (including any attached or
&

Re: [Openstack] Pondering multi-tenant needs in nova.

[Diego Parrilla Santamaría]

Hi Monsyne,

it's a very interesting topic and I'm curious about the reason why you
are using the Flat Networking set up. From the conversations in other
threads it seems the Service Providers prefer different networking
approaches: VLAN oriented basically.

Regards
Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Thu, Feb 3, 2011 at 2:37 AM, Monsyne Dragon  wrote:
> I am sorting out some possible implementations for the
> multi-tenant-accounting blueprint, and the related system-usage-records bp,
> and I just wanted to run this by anyone interested in such matters.
>
> Basically, for multitenant purposes we need to introduce the concept of an
> 'account' in nova, representing a customer,  that basically acts as a label
> for a group of resources (instances, etc), and for access control (i.e
> customer a cannot mess w/ customer b's stuff)
>
> There was some confusion on how best to implement this, in relation to
> nova's project concept.  Projects are kind of like what we want an account
> to be, but there are some associations (like one project per network) which
> are not valid for our flat networking setup.  I am kind of straw-polling on
> which is better here:
>
> The options are:
> 1) Create a new 'account' concept in nova,  with an account basically being
> a subgroup of a project (providers would use a single, default project, with
> additional projects added if needed for separate brands, or resellers, etc),
> add in access control per account as well as project, and make sure
> apis/auth specify account appropriately,  have some way for a default
> account to used (per project) so account doesn't get in the way for
> non-multitenant users.
>
> 2) having account == nova's "project", and changing the network
> associations, etc so projects can support our model (as well as current
> models).  Support for associating accounts (projects) together for
> resellers, etc would either be delegated outside of nova or added later
> (it's not a current requirement).
>
> In either case, accounts would be identified by name, which would  be an
> opaque string an outside system/person would assign, and could structure to
> their needs (ie. for associating accounts with common prefixes, etc)
>
> --
>
> --
>    -Monsyne Dragon
>    work:         210-312-4190
>    mobile        210-441-0965
>    google voice: 210-338-0336
>
>
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at ab...@rackspace.com, and delete the original message.
> Your cooperation is appreciated.
>
>
> ___
> 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] Multi-NIC support to Cactus

[Diego Parrilla Santamaría]

I think multi-NIC support for virtual instances is great if you can
design complex virtual network architectures, which is not the case
now in Nova.

So a first step could be multiple VLANs per zone. This requirement
would cascade new needs like virtual switches, QoS in virtual ports,
and of course multi-NIC support.

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Wed, Feb 2, 2011 at 2:05 PM, Ewan Mellor  wrote:
> That's a good question.  Multi-NIC support could be separated out from the 
> rest of the network-service blueprint, but I don't know whether it would be 
> useful to do so.
>
> I assume that the tenant will not be able to configure any rich network 
> topologies until network-service is done.  If that is true, what else would 
> you do with multi-NIC support?  And how do you imagine that it would work?
>
> Thanks,
>
> Ewan.
>
>> -Original Message-
>> From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
>> [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
>> On Behalf Of masumo...@nttdata.co.jp
>> Sent: 02 February 2011 06:34
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] Multi-NIC support to Cactus
>>
>> Hello,
>>
>> Regarding to the blueprint to Cactus,
>> I found 2 blueprints that may be related to multi-NIC.
>> ( I expect instances can have multiple vnic. )
>>
>> 1. <https://blueprints.launchpad.net/nova/+spec/multi-nic>
>> 2. <https://blueprints.launchpad.net/nova/+spec/multinic-libvirt>
>>
>> Q1. New network model topic and multi-nic support topic will be
>> discussed as different topics for Cactus.
>> A new netowk model is deferred to Diablo but multi-NIC support may be
>> included in Cactus, am I following to current discussion?
>>
>> Q2. If so, looking back to discussions till now, multi-nic might be
>> supported to Xenserver and KVM to Cactus?
>> I know we are not sure till any blueprint be approved, my team is
>> curious to KVM multi-nic support.
>>
>> Regards,
>> Kei Masumoto
>>
>> ___
>> 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] Glance x-image-meta-type raw vs machine

[Diego Parrilla Santamaría]

2011/1/14 Jay Pipes 

> 2011/1/14 Diego Parrilla Santamaría :
> > Well... VMX is probably too VMware oriented. My only concern about this
> kind
> > of proprietary parameter file is you don't really have the chance to
> control
> > its lifecycle. New versions, changes... and developers lagging behind of
> > this changes. It can be a nightmare.
> > But this is more a decision of Product Management than a technical
> > decision... from my perspective. From a pure user perspective, the more
> > options the better, of course.
> > BTW, I think we did a good job in Abicloud about virtual disk formats and
> > virtual images:
> http://abiquo.org/display/ABI16/Virtual+Images+Introduction
>
> Helpful link, thanks Diego :)
>
> Followup question, based partly on the table of supported disk
> formats: instead of the general VMDK as a disk format, should we have
> a more broken-down format for, say, sparse VMDK?
>
> In other words, how fine-grained should the metadata about an image in
> Glance be?
>
>
Jay,

I think VMDK subtypes are very relevant information and has to be indicated
before a deployment. Just an example: if you try to deploy a streamOptimized
or even some sparse formats directly to VMware ESXi they won't work, and
troubleshooting for newbies can be complicated.

I'm not very famliar with Glance yet. So may be some of my asumptions can
sound stupid...

I guess that one of the main purpose of Glance is to deal with Object
Storage Services (Swift or S3 for example) because they are the best
candidates to store virtual images. I think this is a 'necessary evil': such
a big images must be stored somewhere.

What I don't really get is how Glance is going to deal with all the
different virtual images formats supported for the different hypervisors. I
mean, who is going to convert from virtual image format X to the virtual
image format needed by hypervisor Y? Is Glance responsible for this or the
Compute Node? May be if you explain me a little bit how it will work I can
be more helpful. I'm still with Austin and I will start to work on the Bexar
branch very soon.

Regards
Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29


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

Re: [Openstack] Glance x-image-meta-type raw vs machine

[Diego Parrilla Santamaría]

2011/1/13 Erik Carlin 

> I would just call it VMDK.  That's what Vmware
> (http://www.vmware.com/technical-resources/interfaces/vmdk.html) and
> everyone else calls it, even though there may be extra files to support
> it.  We're just naming the disk format here.
>
>
There are several subtypes of VMDK disk formats: monolithic, sparse,
streamOptimized and more... some have the information selfcontained, other
needs parameter files, other are compressed, some cannot be executed in
VMware ESX without converting it...

If I am not wrong Glance is like a repository of images to serve the
computing nodes. So probably the sparseOptimized format should be the right
VMDK to use. The problem is it has to be converted to a runnable VMDK type
before deploying it.

My 2 cents,
Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29



> We had also talked about the IMG disk format to support AMIs but RAW is
> the same thing so we are covered there.
>
> Erik
>
>
>
> On 1/13/11 9:15 AM, "Jay Pipes"  wrote:
>
> >2011/1/13 Diego Parrilla Santamaría  >:
> >> An appliance is the combination of metadata describing the virtual
> >>machine
> >> plus the virtual disks. The standard format in the virtualization
> >>industry
> >> is OVF. Basically, differs from VMX+VMDK(s) because it has a XML format
> >>that
> >> describes the virtual machine (and little bit its environment like
> >> firewalling, policies, etc...).
> >> VMX is VMware specific, and OVF is vendor agnostic (or should be...).
> >>From
> >> my perspective VMX + VMDK(s) is not an appliance format, but this is the
> >> kind of topic for a long discussion ;-)
> >> If you are looking for a simple way to describe the virtual machine
> >> parameters for an appliance, check OVF specs to get some inspiration. I
> >> think OVF full spec is overkill because the simpler approach of Nova.
> >
> >Thanks for the explanation, Diego! Much appreciated.
> >
> >The question arises because we are wondering what information to store
> >in Glance's registry that describes an image. I had proposed the
> >following, with additions from John Purrier:
> >
> >disk_format: choices: VHD, VDI, VMDK, RAW, & QCOW2
> >appliance_format: choices: OVF, OVA, & AMI.
> >
> >Do you agree that we should put VMX in the list of appliance formats,
> >as Ewan Mellor suggested?
> >
> >Cheers!
> >jay
> >
> >___
> >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] Glance x-image-meta-type raw vs machine

[Diego Parrilla Santamaría]

2011/1/13 Jay Pipes 

> 2011/1/13 Diego Parrilla Santamaría :
> > An appliance is the combination of metadata describing the virtual
> machine
> > plus the virtual disks. The standard format in the virtualization
> industry
> > is OVF. Basically, differs from VMX+VMDK(s) because it has a XML format
> that
> > describes the virtual machine (and little bit its environment like
> > firewalling, policies, etc...).
> > VMX is VMware specific, and OVF is vendor agnostic (or should be...).
> From
> > my perspective VMX + VMDK(s) is not an appliance format, but this is the
> > kind of topic for a long discussion ;-)
> > If you are looking for a simple way to describe the virtual machine
> > parameters for an appliance, check OVF specs to get some inspiration. I
> > think OVF full spec is overkill because the simpler approach of Nova.
>
> Thanks for the explanation, Diego! Much appreciated.
>
> The question arises because we are wondering what information to store
> in Glance's registry that describes an image. I had proposed the
> following, with additions from John Purrier:
>
> disk_format: choices: VHD, VDI, VMDK, RAW, & QCOW2
> appliance_format: choices: OVF, OVA, & AMI.
>
> Do you agree that we should put VMX in the list of appliance formats,
> as Ewan Mellor suggested?
>
>
Well... VMX is probably too VMware oriented. My only concern about this kind
of proprietary parameter file is you don't really have the chance to control
its lifecycle. New versions, changes... and developers lagging behind of
this changes. It can be a nightmare.

But this is more a decision of Product Management than a technical
decision... from my perspective. From a pure user perspective, the more
options the better, of course.

BTW, I think we did a good job in Abicloud about virtual disk formats and
virtual images: http://abiquo.org/display/ABI16/Virtual+Images+Introduction

Cheers
Diego



-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29






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

Re: [Openstack] Glance x-image-meta-type raw vs machine

[Diego Parrilla Santamaría]

An appliance is the combination of metadata describing the virtual machine
plus the virtual disks. The standard format in the virtualization industry
is OVF. Basically, differs from VMX+VMDK(s) because it has a XML format that
describes the virtual machine (and little bit its environment like
firewalling, policies, etc...).

VMX is VMware specific, and OVF is vendor agnostic (or should be...). From
my perspective VMX + VMDK(s) is not an appliance format, but this is the
kind of topic for a long discussion ;-)

If you are looking for a simple way to describe the virtual machine
parameters for an appliance, check OVF specs to get some inspiration. I
think OVF full spec is overkill because the simpler approach of Nova.

Diego

-
Diego Parrilla
nubeblog.com | nubeb...@nubeblog.com | twitter.com/nubeblog
+34 649 94 43 29




On Thu, Jan 13, 2011 at 3:32 PM, Jay Pipes  wrote:

> On Wed, Jan 12, 2011 at 5:33 PM, Ewan Mellor 
> wrote:
> > Is there a name for the .vmx + .vmdk combination (i.e. a normal VMware VM
> format)?  Maybe just "VMX" as an appliance format?
>
> Sorry for the probably ignorant question here (I'm pretty ignorant to
> a lot of the virtualization details :( ). From Googling, it seems that
> the VMX file is merely a configuration file fed to vmware along with a
> VMDK when creating a virtual machine.  Is this considered an appliance
> format? Thanks in advance,
>
> -jay
>
> >
> >> -Original Message-
> >> From: John Purrier [mailto:j...@openstack.org]
> >> Sent: 10 January 2011 08:59
> >> To: 'Jay Pipes'
> >> Cc: Ewan Mellor; openstack@lists.launchpad.net
> >> Subject: RE: [Openstack] Glance x-image-meta-type raw vs machine
> >>
> >> Jay, this makes a lot of sense. For disk formats I would suggest: VHD,
> >> VDI, VMDK, RAW, & QCOW2. For the appliance formats: OVF, OVA, & AMI.
> >>
> >> Conversion within Glance will need to be able to handle both disk image
> >> conversion and appliance format conversion.
> >>
> >> John
> >>
> >> -Original Message-
> >> From: Jay Pipes [mailto:jaypi...@gmail.com]
> >> Sent: Monday, January 10, 2011 10:26 AM
> >> To: John Purrier
> >> Cc: Ewan Mellor; openstack@lists.launchpad.net
> >> Subject: Re: [Openstack] Glance x-image-meta-type raw vs machine
> >>
> >> And I think we need to come to an agreement on the terms used here...
> >>
> >> What is a "type" of virtual image? Do we mean a *disk* image format?
> >> Do we mean a *metadata envelope* type (OVF, AMI, etc)? Do we mean some
> >> "type" of system image or image part (kernel, ramdisk, etc)?
> >>
> >> What Glance is serving/registering is really called a *virtual
> >> appliance*, as described in this article:
> >> http://en.wikipedia.org/wiki/Virtual_appliance
> >>
> >> Proposal:
> >>
> >> Change the Image model to have these following fields, instead of the
> >> existing "type" column:
> >>
> >> disk_format -- choice between ('VHD', 'VDI', 'VMDK')
> >> appliance_file_format -- choice between ('AMI','OVF')
> >>
> >> Thoughts?
> >> -jay
> >>
> >> On Mon, Jan 10, 2011 at 11:11 AM, John Purrier 
> >> wrote:
> >> > My 2 cents... We need to define a transport-neutral specification
> >> that allows us to encapsulate and copy/move a variety of virtual image
> >> formats, this should be based on OVF. The envelope can contain both the
> >> actual image as well as any required meta-data.
> >> >
> >> > The image elements specified are very AMI specific, we should
> >> generalize to be able to indicate the type of virtual image (i.e. AMI,
> >> VHD, etc.). A test for POC can be a service that takes the data in the
> >> OVF or what is stored in Glance to convert between formats. If we do
> >> this correctly all of the required data will be available at the
> >> correct point in the flow.
> >> >
> >> > Don't know if this is directly applicable to the discussion point
> >> below, but it is important that we get the fundamental
> >> design/architecture concepts in place moving forward.
> >> >
> >> > John
> >> >
> >> > -Original Message-
> >> > From: openstack-bounces+john=openstack@lists.launchpad.net
> >> [mailto:openstack-bounces+john =openstack.org
> @lists.launchpad.net] On
> >> Behalf Of Jay Pipes
> >>