Re: [Openstack] [Cinder] command to list volume-group detected/managed by cinder

[Marco CONSONNI]

Hello Ahmed,

it seems like we are facing the same problems!

I was able to install cinder and you can find the instructions here
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html
.

The instructions still have some errors and/or miss some info you can find
reading these bugs that are still open:

- https://bugs.launchpad.net/openstack-manuals/+bug/1078057
- https://bugs.launchpad.net/openstack-manuals/+bug/1078353

This installation uses tgt and I experimented only that one.

To my knowledge, there's no cinder command for listing or showing the
volume group cinder is currently using. In my opinion, this makes sense:
the volume group is something that makes sense only in the case you are
using tgt as virtualization technology for supporting virtual volumes but
this is incidental.
In case, in the future, you use a different technology, maybe the volume
group concept disappears.
I mean, tgt (the enabling technology) needs a volume group for working but
the purpose of cinder is to provide volumes to users independently on how
they are implemented.

Anyway, if you what a complete list of cinder commands, just type

*$ cinder help*

In case you want to know more on a single command (the line above gives the
whole list), type:

*$ cinder help *

For example

*$ cinder help show*

gives information on the syntax and the semantics of command "cinder show".

BTW: this instructions are also valid for other CLIs like nova, keystone
and quantum.

Adding a new volume group in addition to cinder-volumes?

To be honest I don't know. It depends on how tgt works (
http://stgt.sourceforge.net/).

On the other hand, I think that if your goal is to add storage to an
already in place infrastructure, then you probably need to add physical
volumes to cinder-volumes volume group.
I'm not an expert on this field, but I think you've got to investigate vg
(volume group) commands like vgscan, vgextend (I presume this is the one
you need to use for adding storage to an existing volume group), etc...

Caveat: read very carefully this bug report
https://bugs.launchpad.net/openstack-manuals/+bug/1078353.

Regards,
Marco.












On Wed, Dec 5, 2012 at 12:02 AM, Ahmed Al-Mehdi wrote:

> Hello,
>
> In my setup, cinder.conf is set as follows:
>
> root@novato:/etc/cinder# cat cinder.conf
> [DEFAULT]
> rootwrap_config=/etc/cinder/rootwrap.conf
> sql_connection = mysql://cinderUser:cinderPass@10.176.20.102/cinder
> api_paste_confg = /etc/cinder/api-paste.ini
> iscsi_helper=ietadm
> volume_name_template = volume-%s
> volume_group = cinder-volumes
> verbose = True
> auth_strategy = keystone
> #osapi_volume_listen_port=5900
>
> root@novato:/etc/cinder# grep -nsir cinder  /etc/iet/*
> root@novato:/etc/cinder# grep -nsir cinder  /etc/tgt/*
> /etc/tgt/conf.d/cinder_tgt.conf:1:include /var/lib/cinder/volumes/*
>
>
> I have a few cinder related questions:
> - Which iSCSI target is officially supported / tested in Folsom release -
> IET (http://sourceforge.net/projects/iscsitarget/files/)  or tgt (
> http://sourceforge.net/projects/iscsitarget/files/).  If both are
> supported, what is the appropriate value for  "volume_driver" and
> "iscsi_helper" in cinder.conf  for either of them.  Any docs explaining
> this?
>
> - Will Cinder create an internal ID (representation) for volume_group -
> "cinder-volumes"?
>
> - What cinder cli command can I issue to get info on the volume_group -
> "cinder-volumes"?
>
> - Is there a way I can add an additional volume-group, e.g
> "cinder-volumes2"?
>
> I read through the doc at
> http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_volumes.html,
> but did not find answers to the above.
>
> Thank you very much in advance.
>
> Regards,
> Ahmed.
>
>
> ___
> 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] [Cinder] New volume status stuck at "Creating" after creation in Horizon

[Huang Zhiteng]

Can you check the cinder scheduler log?

On Wed, Dec 5, 2012 at 1:44 AM, Ahmed Al-Mehdi  wrote:
> Hello,
>
> I setup a two node OpenStack setup, one controller-node and one
> compute-node.  I am using Quantum, Cinder services, and KVM for
> virtualization.  I am running into an issue creating a volume through
> Horizon which I will attach to a VM later on.  The status of volume in
> Horizon is stuck at "Creating".  The output of "cinder list" shows nothing.
>
> The iscsi service is setup properly, as far as I can tell.  I feel there is
> a communication issue between the openstack services.
>
> No log entry in cinder-volume.log.
>
> However, cinder-scheduler.log has the following entry:
>
> 2012-12-04 09:05:02 23552 DEBUG cinder.openstack.common.rpc.amqp [-]
> received {u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
> u'req-1b122042-c3e4-4c1e-8285-ad148c8c2367', u'_context
> _quota_class': None, u'args': {u'topic': u'cinder-volume', u'image_id':
> None, u'snapshot_id': None, u'volume_id':
> u'9dd360bf-9ef2-499f-ac6e-893abf5dc5ce'}, u'_context_auth_token':
> '', u'_co
> ntext_is_admin': False, u'_context_project_id':
> u'70e5c14a28a14666a86e85b62ca6ae18', u'_context_timestamp':
> u'2012-12-04T17:05:02.375789', u'_context_read_deleted': u'no',
> u'_context_user_id': u'386d0
> f02d6d045e7ba49d8edac7bb43f', u'method': u'create_volume',
> u'_context_remote_address': u'10.176.20.102'} _safe_log
> /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/common.py:195
> 2012-12-04 09:05:02 23552 DEBUG cinder.openstack.common.rpc.amqp [-]
> unpacked context: {'user_id': u'386d0f02d6d045e7ba49d8edac7bb43f', 'roles':
> [u'Member', u'admin'], 'timestamp': u'2012-12-04T17:05:
> 02.375789', 'auth_token': '', 'remote_address': u'10.176.20.102',
> 'quota_class': None, 'is_admin': False, 'request_id':
> u'req-1b122042-c3e4-4c1e-8285-ad148c8c2367', 'project_id': u'70e5c14a
> 28a14666a86e85b62ca6ae18', 'read_deleted': u'no'} _safe_log
> /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/common.py:195
> 2012-12-04 09:05:02 23552 ERROR cinder.openstack.common.rpc.amqp [-]
> Exception during message handling
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp Traceback
> (most recent call last):
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py", line
> 276, in _process_data
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp rval =
> self.proxy.dispatch(ctxt, version, method, **args)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py",
> line 145, in dispatch
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
> getattr(proxyobj, method)(ctxt, **kwargs)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/scheduler/manager.py", line 98, in
> _schedule
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
> db.volume_update(context, volume_id, {'status': 'error'})
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/db/api.py", line 256, in
> volume_update
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
> IMPL.volume_update(context, volume_id, values)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 124, in
> wrapper
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
> f(*args, **kwargs)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 1071,
> in volume_update
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
> volume_ref = volume_get(context, volume_id, session=session)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 124, in
> wrapper
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
> f(*args, **kwargs)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
> "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 1014,
> in volume_get
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp raise
> exception.VolumeNotFound(volume_id=volume_id)
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
> VolumeNotFound: Volume 9dd360bf-9ef2-499f-ac6e-893abf5dc5ce could not be
> found.
> 2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
>
>
> Has anyone run into this issue.  Can I issue some cinder-* cli command to
> get more info about the issue.
> Any help would be very appreciated.
>
> Thank you,
> Ahmed.
>
>
> ___

[Openstack] Announcing OpenStack Day, 15th December, Bangalore India

[Atul Jha]

Hi all,

We are organizing one day event on OpenStack in Bangalore India.
Schedule and registration information is available on 
http://www.openstack.org/blog/2012/12/announcing-openstack-day-15-december-bangalore-india/

If your in town you should attend it if your team is based in India you should 
spread the word about the event and ask them to attend it.
We are trying to spread word about OpenStack here and everyone`s help is much 
needed/appreciated.


Thanks,

Atul Jha
http://www.csscorp.com/common/email-disclaimer.php

___
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] [quantum]switch vm between different network

[spring]

Hi guys,
can you detach a vm from one network and attach it to another network? how
do you do that? thanks
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Cinder] command to list volume-group detected/managed by cinder

[Ahmed Al-Mehdi]

Hello,

In my setup, cinder.conf is set as follows:

root@novato:/etc/cinder# cat cinder.conf
[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinderUser:cinderPass@10.176.20.102/cinder
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper=ietadm
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
#osapi_volume_listen_port=5900

root@novato:/etc/cinder# grep -nsir cinder  /etc/iet/*
root@novato:/etc/cinder# grep -nsir cinder  /etc/tgt/*
/etc/tgt/conf.d/cinder_tgt.conf:1:include /var/lib/cinder/volumes/*


I have a few cinder related questions:
- Which iSCSI target is officially supported / tested in Folsom release -
IET (http://sourceforge.net/projects/iscsitarget/files/)  or tgt (
http://sourceforge.net/projects/iscsitarget/files/).  If both are
supported, what is the appropriate value for  "volume_driver" and
"iscsi_helper" in cinder.conf  for either of them.  Any docs explaining
this?

- Will Cinder create an internal ID (representation) for volume_group -
"cinder-volumes"?

- What cinder cli command can I issue to get info on the volume_group -
"cinder-volumes"?

- Is there a way I can add an additional volume-group, e.g
"cinder-volumes2"?

I read through the doc at
http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_volumes.html,
but did not find answers to the above.

Thank you very much in advance.

Regards,
Ahmed.
___
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] Blueprint proposal: Drop setuptools_git for including data/config files

[Nah, Zhongyue]

Is it possible to generate a MANIFEST.in file using setuptools-git? Would that 
solve simplicity and efficiency?

Sent from my iPhone

On Dec 4, 2012, at 9:07 PM, "Thierry Carrez"  wrote:

> Sascha Peilicke wrote:
>> Currently, the majority of OpenStack components make use of the
>> Python module "setuptools_git" in order to install additional
>> configuration files. This is basically the same functionality that
>> the MANIFEST.in file (setuptools/distribute) provides, but
>> automatic.
> 
> Note: This is a development topic, it should (have) be(en) posted to
> openstack-dev to reach the appropriate audience. Please follow-up there.
> 
>> However, we recently discovered that this approach has issues from
>> a packaging perspective. We weren't getting all the data/config
>> files that the python package usually gets even though we were
>> running the same commands:
>> 
>> $ python setup.py build
>> 
>> followed by:
>> 
>> $ python setup.py install --skip-build
>> 
>> We are building RPM packages from release tarballs (such as [1]),
>> which of course don't include the .git directory. Therefore the
>> setuptools_git approach can't do its magic, thus our package builds
>> get wrong results. Having OpenStack components rely on
>> setuptools_git at build time means we have to distribute the whole
>> git repository along with the source code tarball. Of course this
>> makes no sense, since it would increase the size of release
>> tarballs dramatically and won't get shipped in distributions
>> anyway.Therefore, we (and potentially other distribution vendors)
>> would have to track these files manually in our RPM spec files. 
>> Some reviews have already been opened on the topic (admittedly
>> before we discovered the real issue). Given the different outcome
>> of each review it seems that not everybody is aware that
>> setuptools_git is used or of what it does.
>> 
>> https://review.openstack.org/#/c/17122/ (ceilometer) - this one
>> got accepted before we knew what was going on
>> 
>> https://review.openstack.org/#/c/17347/ (cinder) - abandoned until
>> the situation is clarified
>> 
>> https://review.openstack.org/#/c/17355/ (nova) - rejected
>> 
>> So the better solution would be to stop using setuptools_git and
>> just include all the data/config files that are meant to be
>> distributed in the MANIFEST.in file. This is what every Python
>> developer should know about and has the benefit of increased
>> transparency about what gets installed and what not. We created a
>> blueprint to track this [2].
>> 
>> Thoughts?
> 
> A bit of history here:
> 
> We used to rely on MANIFEST.in to list all files, but people routinely
> forgot to add new files to it. Apparently "every Python developer"
> doesn't know (or care) about this. The end result was that we
> discovered very late (sometimes after the release itself) that we
> built incomplete tarballs. As a quick search[1] shows, I have
> personally filed 27 bugs so far on the subject, so it's not a corner case.
> 
> [1] http://bit.ly/TDim7U
> 
> Relying on setuptools_git instead allows to avoid that issue
> altogether. The projects that adopted it became a non-issue. The
> projects that didn't adopt it yet are still a problem. I was about to
> push setuptools_git support to projects that don't use it yet.
> 
> In summary, I would hate it if we went back to the previous situation.
> I'm not personally attached to setuptools_git, but any proposed
> replacement solution should keep its simplicity.
> 
> -- 
> 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] [Cinder] New volume status stuck at "Creating" after creation in Horizon

[Ahmed Al-Mehdi]

In cider-api.log, I see the following messages when the volume was created,
suggesting Horizon has instructed cinder to create the volume (size 3 GB):

2012-12-04 09:05:02 AUDIT cinder.api.openstack.volume.volumes
[req-1b122042-c3e4-4c1e-8285-ad148c8c2367 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] Create volume of 3 GB
2012-12-04 09:05:02 DEBUG cinder.quota
[req-1b122042-c3e4-4c1e-8285-ad148c8c2367 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] Created reservations
['c9ab451b-b464-46f1-9735-66494
8bcfe2f', '1c3d4643-e9a1-4438-9287-dc2d3c5ed43f'] reserve
/usr/lib/python2.7/dist-packages/cinder/quota.py:663
2012-12-04 09:05:02 5893 DEBUG cinder.openstack.common.rpc.amqp [-] Making
asynchronous cast on cinder-scheduler... cast
/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py:377
2012-12-04 09:05:02 5893 DEBUG cinder.openstack.common.rpc.amqp [-] Pool
creating new connection create
/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py:58
2012-12-04 09:05:02 5893 INFO cinder.openstack.common.rpc.common [-]
Connected to AMQP server on localhost:5672
2012-12-04 09:05:02 AUDIT cinder.api.openstack.volume.volumes
[req-1b122042-c3e4-4c1e-8285-ad148c8c2367 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] vol={'availability_zone': 'no
va', 'terminated_at': None, 'updated_at': None, 'provider_auth': None,
'snapshot_id': None, 'ec2_id': None, 'mountpoint': None, 'deleted_at':
None, 'id': '9dd360bf-9ef2-499f-ac6e-893abf5dc5ce', 'size'
: 3, 'user_id': u'386d0f02d6d045e7ba49d8edac7bb43f', 'attach_time': None,
'display_description': u'First test volume (iscsi)', 'project_id':
u'70e5c14a28a14666a86e85b62ca6ae18', 'launched_at': None, '
scheduled_at': None, 'status': 'creating', 'volume_type_id': None,
'deleted': False, 'provider_location': None, 'host': None, 'display_name':
u'myvol1', 'instance_uuid': None, 'created_at': datetime.d
atetime(2012, 12, 4, 17, 5, 2, 471475), 'attach_status': 'detached'}
2012-12-04 09:05:02 INFO cinder.api.openstack.wsgi
[req-1b122042-c3e4-4c1e-8285-ad148c8c2367 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] http://10.176.20.102:8776/v1/70e5c14a28a
14666a86e85b62ca6ae18/volumes returned with HTTP 200
2012-12-04 09:05:02 INFO cinder.api.openstack.wsgi
[req-c6c7ec3a-c2cd-4aa1-851a-1aa3bd218341 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] GET http://10.176.20.102:8776/v1/70e5c14
a28a14666a86e85b62ca6ae18/volumes/detail
2012-12-04 09:05:02 DEBUG cinder.api.openstack.wsgi
[req-c6c7ec3a-c2cd-4aa1-851a-1aa3bd218341 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] Unrecognized Content-Type provided in r
equest get_body
/usr/lib/python2.7/dist-packages/cinder/api/openstack/wsgi.py:695
2012-12-04 09:05:02 DEBUG cinder.api.openstack.volume.volumes
[req-c6c7ec3a-c2cd-4aa1-851a-1aa3bd218341 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] Removing options '' from quer
y remove_invalid_options
/usr/lib/python2.7/dist-packages/cinder/api/openstack/volume/volumes.py:356
2012-12-04 09:05:02 AUDIT cinder.api.openstack.volume.volumes
[req-c6c7ec3a-c2cd-4aa1-851a-1aa3bd218341 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] vol=
2012-12-04 09:05:02 INFO cinder.api.openstack.wsgi
[req-c6c7ec3a-c2cd-4aa1-851a-1aa3bd218341 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] http://10.176.20.102:8776/v1/70e5c14a28a
14666a86e85b62ca6ae18/volumes/detail returned with HTTP 200

And then the following three messages repeated every minute or two from
then onwards:

2012-12-04 09:05:03 INFO cinder.api.openstack.wsgi
[req-0a3b9032-b32a-4858-986e-741f213b8c38 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] GET http://10.176.20.102:8776/v1/70e5c14
a28a14666a86e85b62ca6ae18/volumes/9dd360bf-9ef2-499f-ac6e-893abf5dc5ce
2012-12-04 09:05:03 DEBUG cinder.api.openstack.wsgi
[req-0a3b9032-b32a-4858-986e-741f213b8c38 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] Unrecognized Content-Type provided in r
equest get_body
/usr/lib/python2.7/dist-packages/cinder/api/openstack/wsgi.py:695
2012-12-04 09:05:03 AUDIT cinder.api.openstack.volume.volumes
[req-0a3b9032-b32a-4858-986e-741f213b8c38 386d0f02d6d045e7ba49d8edac7bb43f
70e5c14a28a14666a86e85b62ca6ae18] vol={'volume_metadata': [], '
availability_zone': u'nova', 'terminated_at': None, 'updated_at': None,
'snapshot_id': None, 'ec2_id': None, 'mountpoint': None, 'deleted_at':
None, 'id': u'9dd360bf-9ef2-499f-ac6e-893abf5dc5ce', 'siz
e': 3L, 'user_id': u'386d0f02d6d045e7ba49d8edac7bb43f', 'attach_time':
None, 'display_description': u'First test volume (iscsi)', 'project_id':
u'70e5c14a28a14666a86e85b62ca6ae18', 'launched_at': None
, 'scheduled_at': None, 'status': u'creating', 'volume_type_id': None,
'deleted': False, 'provider_location': None, 'host': None, 'provider_auth':
None, 'display_name': u'myvol1', 'instance_uuid': Non
e, 'created_at': datet

Re: [Openstack] Will Heat Work Without systemd (i.e. will it work with init)?

[Rickard, Ronald]

I am attempting to install/configure Heat on RHEL 6.3.  This server already has 
other OpenStack (Essex release) products installed: nova, glance, keystone, 
etc.  I built the RPMs for Heat (v7) and Heat JEOS (v7) by commenting out the 
requirements on systemd-units and the systemd unit files in the heat.spec 
because RHEL 6.3 uses init instead of systemd.  I am thinking I can replace 
these systemd unit files with init.d scripts to startup Heat.  I installed the 
RPMs and am at the step in the process where I am creating a JEOS with 
heat_jeos:

heat-jeos -y create F17-x86_64-cfntools -register-with-glance

It takes almost 10 minutes and I see activity in the /var/lib/oz/isos and 
/var/lib/oz/isocontent directory, but eventually, I see the following error:

Traceback (most recent call last):
  File "/usr/bin/heat-jeos", line 375, in 
main()
  File "/usr/bin/heat-jeos", line 363, in main
result = cmd(opts, args)
  File "/usr/bin/heat-jeos", line 139, in command_create
build_jeos(get_oz_guest(final_tdl))
  File "/usr/lib/python2.6/site-packages/heat_jeos/utils.py", line 132, in 
build_jeos
guest.customize(libvirt_xml)
  File "/usr/lib/python2.6/site-packages/oz/RedHat.py", line 1166, in customize
return self._internal_customize(libvirt_xml, "no")
  File "/usr/lib/python2.6/site-packages/oz/RedHat.py", line 1150, in 
_internal_customize
self.do_customize(guestaddr)
  File "/usr/lib/python2.6/site-packages/oz/RedHat.py", line 1104, in 
do_customize
self.guest_execute_command(guestaddr, content)
  File "/usr/lib/python2.6/site-packages/oz/RedHat.py", line 474, in 
guest_execute_command
command, timeout, tunnels)
  File "/usr/lib/python2.6/site-packages/oz/ozutil.py", line 362, in 
ssh_execute_command
return subprocess_check_output(cmd)
  File "/usr/lib/python2.6/site-packages/oz/ozutil.py", line 329, in 
subprocess_check_output
raise SubprocessException("'%s' failed(%d): %s" % (cmd, retcode, stderr), 
retcode)
oz.ozutil.SubprocessException: 'ssh -i /etc/oz/id_rsa-icicle-gen -F /dev/null 
-o ServerAliveInterval=30 -o StrictHostKeyChecking=no -o ConnectTimeout=10 -o 
UserKnownHostsFile=/dev/null -o PasswordAuthentication=no root@W.X.Y.Z yum -y 
update fedora-release
yum -y install yum-plugin-fastestmirror cloud-init python-psutil python-boto
yum -y update
sed --in-place -e s/Type=oneshot/"Type=oneshot\nTimeoutSec=0"/ 
/lib/systemd/system/cloud-final.service' failed(2): Warning: Permanently added 
'W.X.Y.Z' (RSA) to the list of known hosts.
Error: Cannot retrieve metalink for repository: fedora. Please verify its path 
and try again
Error: Cannot retrieve metalink for repository: fedora. Please verify its path 
and try again
Error: Cannot retrieve metalink for repository: fedora. Please verify its path 
and try again
sed: can't read /lib/systemd/system/cloud-final.service: No such file or 
directory

Thanks,
Ron

From: Steve Baker [mailto:sba...@redhat.com]
Sent: Monday, December 03, 2012 2:09 PM
To: openstack@lists.launchpad.net
Cc: Rickard, Ronald
Subject: Re: [Openstack] Will Heat Work Without systemd (i.e. will it work with 
init)?

On 12/04/2012 08:44 AM, Rickard, Ronald wrote:
It appears Heat is being developed for OSes that support systemd.  Will Heat 
also work on systems that use init?
It is not our intention to only support systemd based distros. It would be most 
helpful if you could describe the details of your issues in our Launchpad:
https://bugs.launchpad.net/heat

or post them to this list.

cheers
___
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 deploy openstack automatically in your env.

[Joshua Harlow]

For RHEL.

Although its not made for such big purposes as puppet/chef there is the
anvil project.

http://anvil.readthedocs.org/en/latest/

http://anvil.readthedocs.org/en/latest/topics/dev_notes/architecture.html

Its been used at yahoo with RHEL 6.2+ for a while now, not as our
deployment engine but the thing we use pre-deployment to do dev work, run
unit tests, build rpm packages and then handoff to our deployment engine
(internal tech). Try it out, complaints/comments welcome ;)

On 12/3/12 7:19 AM, "Jonathan Proulx"  wrote:

>On Mon, Dec 03, 2012 at 06:21:54PM +0800, Lei Zhang wrote:
>:It is a wired thing that the openstack is a python project. But many
>tools
>:for it are build on ruby?
>
>Puppet (http://puppetlabs.com/) and Chef
>(http://www.opscode.com/chef), the main players in configuration
>management are both written in Ruby and manage more than just
>OpenStack so the code just isn't related
>
>I can't be much help on your origina RHEL question as I run a Debian /
>Ubuntu shop.  But while it is true that deployment tools are better
>tested on Ubuntu, certainly any puppe tor chef based solutions
>*should* work on RHEL if they don't it would be worth reporting their
>failures to the developers of those tools.
>
>There is a Fedora OpenStack wiki at
>http://fedoraproject.org/wiki/OpenStack which is linked from
>http://www.openstack.org/software/start/ which has other RedHat family
>specific links at the bottom of the page
>
>-Jon
>
>:
>:
>:On Mon, Dec 3, 2012 at 5:44 PM, Joe Breu 
>wrote:
>:
>:>  Hi Lei,
>:>
>:>  We have chef cookbooks to install Openstack located at
>:> http://github.com/rcbops/chef-cookbooks.
>:>
>:>   ---
>:> Joseph Breu
>:> Deployment Engineer
>:> Rackspace Private Cloud
>:> 210-312-3508
>:>
>:>  On Dec 3, 2012, at 9:15 AM, Lei Zhang wrote:
>:>
>:>  Hi all,
>:>
>:> I search the internet for days and found several automatically tool.
>:> Including
>:>
>:>- devstack
>:>- puppet+pupet-openstack
>:>- stackops
>:>- OneStack
>:>
>:> But It seems that all the scripts are well tested on ubuntu not RHEL.
>How
>:> could you guys to deploy the openstack automatically, especially on
>RHEL.
>:>  --
>:> Lei Zhang
>:>
>:>  Blog: http://jeffrey4l.github.com
>:> twitter/weibo: @jeffrey4l
>:>
>:>  ___
>:> Mailing list: https://launchpad.net/~openstack
>:> Post to : openstack@lists.launchpad.net
>:> Unsubscribe : https://launchpad.net/~openstack
>:> More help   : https://help.launchpad.net/ListHelp
>:>
>:>
>:>
>:
>:
>:-- 
>:Lei Zhang
>:
>:Blog: http://jeffrey4l.github.com
>:twitter/weibo: @jeffrey4l
>
>:___
>: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] Cloud-Init for Windows

[Alessandro Pilotti]

We just release a new project for initializing Windows cloud instances on 
OpenStack:

http://www.cloudbase.it/cloud-init-for-windows-instances/

Some quick facts about it:

• Supports HTTP and ConfigDriveV2 metadata sources
• Provides out the box: user creation, password injection, static 
networking configuration, hostname, SSH public keys and userdata scripts 
(Powershell, Cmd or Bash)
• It’s highly modular and can be easily extended to provide support for 
more features and metadata sources.
• Works on any hypervisor (Hyper-V, KVM, Xen, etc)
• Works on Windows Server 2003 / 2003 R2 / 2008 / 2008 R2 / 2012 and 
Windows 7 and 8.
• It’s platform independent, meaning that we plan to add other OSs, 
e.g.: FreeBSD
• Written in Python
• Open source, Apache 2 licensed: 
https://github.com/alexpilotti/cloudbase-init

It's currently in beta status, we are looking for help to test it on various 
hypervisor / guest combinations. I'd be glad to answer any question (and fix 
any bug)! :-) 
We did most of our testing so far on Windows 2008 R2 and Windows 2012 using 
ConfigDriveV2 metadata on Grizzly, but we plan to add more platforms to the 
tests soon.

IRC: alexpilotti 


Thanks!

Alessandro Pilotti
Cloudbase Solutions | CEO
-
MVP ASP.Net / IISWindows Azure Insider
Red Hat Certified Engineer 
-





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

[Openstack] [Cinder] New volume status stuck at "Creating" after creation in Horizon

[Ahmed Al-Mehdi]

Hello,

I setup a two node OpenStack setup, one controller-node and one
compute-node.  I am using Quantum, Cinder services, and KVM for
virtualization.  I am running into an issue creating a volume through
Horizon which I will attach to a VM later on.  The status of volume in
Horizon is stuck at "Creating".  The output of "cinder list" shows nothing.

The iscsi service is setup properly, as far as I can tell.  I feel there is
a communication issue between the openstack services.

No log entry in cinder-volume.log.

However, cinder-scheduler.log has the following entry:

2012-12-04 09:05:02 23552 DEBUG cinder.openstack.common.rpc.amqp [-]
received {u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
u'req-1b122042-c3e4-4c1e-8285-ad148c8c2367', u'_context
_quota_class': None, u'args': {u'topic': u'cinder-volume', u'image_id':
None, u'snapshot_id': None, u'volume_id':
u'9dd360bf-9ef2-499f-ac6e-893abf5dc5ce'}, u'_context_auth_token':
'', u'_co
ntext_is_admin': False, u'_context_project_id':
u'70e5c14a28a14666a86e85b62ca6ae18', u'_context_timestamp':
u'2012-12-04T17:05:02.375789', u'_context_read_deleted': u'no',
u'_context_user_id': u'386d0
f02d6d045e7ba49d8edac7bb43f', u'method': u'create_volume',
u'_context_remote_address': u'10.176.20.102'} _safe_log
/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/common.py:195
2012-12-04 09:05:02 23552 DEBUG cinder.openstack.common.rpc.amqp [-]
unpacked context: {'user_id': u'386d0f02d6d045e7ba49d8edac7bb43f', 'roles':
[u'Member', u'admin'], 'timestamp': u'2012-12-04T17:05:
02.375789', 'auth_token': '', 'remote_address':
u'10.176.20.102', 'quota_class': None, 'is_admin': False, 'request_id':
u'req-1b122042-c3e4-4c1e-8285-ad148c8c2367', 'project_id': u'70e5c14a
28a14666a86e85b62ca6ae18', 'read_deleted': u'no'} _safe_log
/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/common.py:195
2012-12-04 09:05:02 23552 ERROR cinder.openstack.common.rpc.amqp [-]
Exception during message handling
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp Traceback
(most recent call last):
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py",
line 276, in _process_data
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp rval =
self.proxy.dispatch(ctxt, version, method, **args)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py",
line 145, in dispatch
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
getattr(proxyobj, method)(ctxt, **kwargs)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/scheduler/manager.py", line 98, in
_schedule
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
db.volume_update(context, volume_id, {'status': 'error'})
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/db/api.py", line 256, in
volume_update
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
IMPL.volume_update(context, volume_id, values)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 124,
in wrapper
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
f(*args, **kwargs)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 1071,
in volume_update
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
volume_ref = volume_get(context, volume_id, session=session)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 124,
in wrapper
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp return
f(*args, **kwargs)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp   File
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 1014,
in volume_get
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp raise
exception.VolumeNotFound(volume_id=volume_id)
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp
VolumeNotFound: Volume 9dd360bf-9ef2-499f-ac6e-893abf5dc5ce could not be
found.
2012-12-04 09:05:02 23552 TRACE cinder.openstack.common.rpc.amqp


Has anyone run into this issue.  Can I issue some cinder-* cli command to
get more info about the issue.
Any help would be very appreciated.

Thank you,
Ahmed.
___
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] Understanding "flavors" of VM

[Ahmed Al-Mehdi]

Hi Marco,

This is really good stuff, thank you very much for helping out.  I am
creating some instances to test out how/where the different storage related
elements are created.

I created two VM instance:

Instance 1 : 20GB boot disk
Instance 2 : 10GB boot disk, 2 GB Ephemeral disk.

root@bodega:/var/lib/nova# ls -lh -R instances
instances:
total 12K
drwxrwxr-x 2 nova nova 4.0K Dec  4 09:01 _base
drwxrwxr-x 2 nova nova 4.0K Nov 28 11:44 instance-0001
drwxrwxr-x 2 nova nova 4.0K Dec  4 09:01 instance-0002

instances/_base:
total 240M
-rw-r--r-- 1 nova nova  40M Dec  4 08:51
8af61c9e86557f7244c6e5a2c45e1177c336bd1f
-rw-r--r-- 1 libvirt-qemu kvm   10G Dec  4 09:01
8af61c9e86557f7244c6e5a2c45e1177c336bd1f_10
-rw-r--r-- 1 nova kvm   20G Dec  4 08:51
8af61c9e86557f7244c6e5a2c45e1177c336bd1f_20
-rw-rw-r-- 1 nova nova 9.4M Nov 28 11:44
8af61c9e86557f7244c6e5a2c45e1177c336bd1f.part
-rw-r--r-- 1 nova nova 2.0G Dec  4 09:01 ephemeral_0_2_None
<==
-rw-r--r-- 1 libvirt-qemu kvm  2.0G Dec  4 09:01 ephemeral_0_2_None_2
<=

instances/instance-0001:
total 1.9M
-rw-rw 1 nova kvm   26K Nov 28 11:45 console.log
-rw-r--r-- 1 libvirt-qemu kvm  1.9M Dec  4 07:01 disk
-rw-rw-r-- 1 nova nova 1.4K Nov 28 11:44 libvirt.xml

instances/instance-0002:
total 1.8M
-rw-rw 1 libvirt-qemu kvm   27K Dec  4 09:02 console.log
-rw-r--r-- 1 libvirt-qemu kvm  1.6M Dec  4 09:03 disk
-rw-r--r-- 1 libvirt-qemu kvm  193K Dec  4 09:01 disk.local
-rw-rw-r-- 1 nova nova 1.6K Dec  4 09:01 libvirt.xml
root@bodega:/var/lib/nova#

It seems all the boot disk and ephemeral disk are created as files in
/var/lib/nova/instance/_base.  I don't understand why there are two files
of size 2GB  (lines marked above with <=).  I will look into that later
on.

I am running into an issue creating a volume for which I will post a
separate message.

Thank you again very much.

Regards,
Ahmed.



On Tue, Dec 4, 2012 at 8:56 AM, Marco CONSONNI  wrote:

> Sorry, the directory you need to check is  /var/lib/nova/instances.
>
> MCo.
>
>
> On Tue, Dec 4, 2012 at 5:54 PM, Marco CONSONNI  wrote:
>
>> Hi Ahmed,
>>
>> very technical questions.
>> I'm not sure my answers are right: I'm just an user...
>>
>> In order to answer, I've just look at what happens and made some guess.
>> Feel free to verify yourself.
>>
>> I'm assuming you are using KVM as I'm doing.
>>
>> The space for the boot disk and the ephemeral disk should be represented
>> as files in the physical node where the VM is hosted.
>> In order to check that, go to directory  /var/lib/nova on the node where
>> the VM is running.
>> As far as I understand, this is where nova (and KVM) keep the running
>> instances' information.
>> You should see a directory for each running instance named as
>> instance-xxx, where xxx uniquely identifies an instance (there are
>> several ways for uniquely identify an instance, this is one of many... but
>> this is a different story).
>> Go into one of these and check what you find.
>>
>> For what concerns nova-scheduler, I don't know what exactly does. I'm
>> afraid that you need to test and see what happens.
>>
>> A nova command can help for inspecting what a node is using, in terms of
>> resources.
>>
>> At the controller node (or any other node where you installed nova
>> client), type the following command substituting OpenStack02 with the name
>> of the node you want to inspect:
>>
>> *$ nova host-describe OpenStack02*
>>
>>
>> +-+--+-+---+-+
>>
>> | HOST| PROJECT  | cpu | memory_mb |
>> disk_gb |
>>
>>
>> +-+--+-+---+-+
>>
>> | OpenStack02 | (total)  | 16  | 24101 | 90
>> |
>>
>> | OpenStack02 | (used_max)   | 13  | 7680  | 0
>> |
>>
>> | OpenStack02 | (used_now)   | 13  | 8192  | 0
>> |
>>
>> | OpenStack02 | 456ec9d355ae4feebe48a2e79e703225 | 4   | 2048  | 0
>> |
>>
>> | OpenStack02 | fb434e07b687494bb669fde23f497970 | 9   | 5632  | 0
>> |
>>
>>
>> +-+--+-+---+-+
>>
>> It return a brief report of the resources currently used by a node.
>>
>> To my knowledge,  the dashboard does not provide a similar page, at the
>> time being.
>>
>> Hope it helps,
>> Marco.
>>
>>
>>
>>
>> On Tue, Dec 4, 2012 at 4:40 PM, Ahmed Al-Mehdi wrote:
>>
>>> Hi Marco,
>>>
>>> Thank you very much for the info, much much clearer.  I was looking for
>>> the boot disk using "ls -l /dev/sd*", but the existence of /dev/vda1
>>> should have given me a clue.
>>>
>>> A few follow up questions:
>>>
>>> - I am assuming the space for the VM boot disk is allocated from the
>>> local hard disk of the physical host on which the VM is instantiated,
>>> right?
>>> - If Yes
>>>- How is the boot disk represented on the phy

Re: [Openstack] resizing instance fails

[John Garbutt]

Hi,

This is interesting:
2012-12-03 14:38:25 ERROR nova.compute.manager 
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] [instance: 
d3dba21b-3877-4da3-a2ab-8128f8515573] VHD coalesce attempts exceeded (5), 
giving up Setting instance vm_state to ERROR

Is it possible to get the logs from your XenServer host to tell us what was 
going wrong when this happened?

What is the version of your server, and I am assuming the VM disks are on an 
EXT3 SR?

John

From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On 
Behalf Of Afef MDHAFFAR
Sent: 03 December 2012 14:42
To: openstack@lists.launchpad.net
Subject: [Openstack] resizing instance fails

Hi all,

when I try to resize a running instance, I get this error:
Is there any way to solve it?


2012-12-03 14:38:25 ERROR nova.compute.manager 
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] [instance: 
d3dba21b-3877-4da3-a2ab-8128f8515573] VHD coalesce attempts exceeded (5), 
giving up Setting instance vm_state to ERROR
2012-12-03 14:38:25 DEBUG nova.manager [-] Running periodic task 
SchedulerManager._expire_reservations from (pid=19093) periodic_tasks 
/opt/stack/nova/nova/manager.py:171
2012-12-03 14:38:25 DEBUG nova.openstack.common.lockutils 
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore 
"compute_resources" for method "update_usage"... from (pid=19070) inner 
/opt/stack/nova/nova/openstack/common/lockutils.py:185
2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] received 
{u'_context_roles': [], u'_context_request_id': 
u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb', u'_context_quota_class': None, 
u'_context_project_name': None, u'_context_service_catalog': None, 
u'_context_user_name': None, u'_context_auth_token': '', u'args': 
{u'service_name': u'compute', u'host': u'computeDomU03', u'capabilities': 
{u'host_name-description': u'Default install of XenServer', u'disk_available': 
230087983104, u'host_hostname': u'compute09', u'supported_instances': 
[[u'x86_64', u'xapi', u'xen'], [u'x86_32p', u'xapi', u'xen'], [u'x86_32', 
u'xapi', u'hvm'], [u'x86_32p', u'xapi', u'hvm'], [u'x86_64', u'xapi', u'hvm']], 
u'host_memory_overhead': 106897408, u'enabled': u'true', u'host_ip': 
u'10.0.1.19', u'host_capabilities': [u'xen-3.0-x86_64', u'xen-3.0-x86_32p', 
u'hvm-3.0-x86_32', u'hvm-3.0-x86_32p', u'hvm-3.0-x86_64'], u'host_uuid': 
u'03433673-d30c-4f8e-94cc-43d53f9c2207', u'host_memory_free': 5261139968, 
u'disk_total': 242124587008, u'host_ip_address': u'10.0.1.166', 
u'hypervisor_hostname': u'compute09', u'host_memory_total': 8589463552, 
u'host_memory_free_computed': 5178503168, u'disk_used': 12036603904, 
u'host_other-config': {u'agent_start_time': u'1353496206.', u'boot_time': 
u'1353496188.', u'no_local_storage': u'true'}, u'host_name-label': 
u'compute09', u'host_cpu_info': {u'physical_features': 
u'---', u'modelname': u'Dual-Core AMD 
Opteron(tm) Processor 2216 HE', u'vendor': u'AuthenticAMD', u'features': 
u'---', u'family': 15, u'maskable': u'no', 
u'cpu_count': 4, u'flags': u'fpu de tsc msr pae cx8 apic cmov pat clflush mmx 
fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl 
extd_apicid pni cx16 hypervisor lahf_lm cmp_legacy extapic cr8_legacy', 
u'stepping': 2, u'model': 65, u'features_after_reboot': 
u'---', u'speed': u'2394.010'}}}, 
u'_context_instance_lock_checked': False, u'_context_is_admin': True, 
u'version': u'2.0', u'_context_project_id': None, u'_context_timestamp': 
u'2012-12-03T14:38:26.342811', u'_context_read_deleted': u'no', 
u'_context_user_id': None, u'method': u'update_service_capabilities', 
u'_context_remote_address': None} from (pid=19093) _safe_log 
/opt/stack/nova/nova/openstack/common/rpc/common.py:195
2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] unpacked context: 
{'project_name': None, 'user_id': None, 'roles': [], 'timestamp': 
u'2012-12-03T14:38:26.342811', 'auth_token': '', 'remote_address': 
None, 'quota_class': None, 'is_admin': True, 'service_catalog': None, 
'request_id': u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb', 
'instance_lock_checked': False, 'project_id': None, 'user_name': None, 
'read_deleted': u'no'} from (pid=19093) _safe_log 
/opt/stack/nova/nova/openstack/common/rpc/common.py:195
2012-12-03 14:38:26 DEBUG nova.scheduler.host_manager 
[req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb None None] Received compute service 
update from (u'computeDomU03', u'compute09'). from (pid=19093) 
update_service_capabilities /opt/stack/nova/nova/scheduler/host_manager.py:340
2012-12-03 14:38:26 DEBUG nova.openstack.common.lockutils 
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore 
"compute_resources" for method "update_usage"... from (pid=19070) inner 
/opt/stack/nova/nova/openstack/common/lockutils.py:185
2012-12-03 14:38:26 ERROR nova

Re: [Openstack] Potential security issue with CHAP

[Kurt Seifried]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/29/2012 03:40 PM, Russell Bryant wrote:
> On 11/29/2012 03:50 AM, Avishay Traeger wrote:
>> 
>> Hi all, Currently, CHAP secrets are managed by Cinder, and passed
>> to Nova for use when attaching volumes.  This means that unless
>> the communication is encrypted, or a separate trusted network is
>> used, CHAP secrets can be sniffed on the wire. Opinions?
> 
> In the future, if you suspect something is a security issue 
> (vulnerability), the public mailing list isn't the best place to
> report it.  :-)  Please use a private bug on launchpad, or send
> someone on the vulnerability management team an encrypted email.
> 
> http://www.openstack.org/projects/openstack-security/
> 
> In this case, I don't think there is a problem here.  A lot of
> sensitive information is passed around between services, via both
> messaging and the REST APIs.  It is certainly important to protect
> these communications via the means you mentioned (trusted network,
> encryption).

Also if appropriate please notify secal...@redhat.com, traditionally
SRT would handle notifying/communications with many upstreams (this
applies more to RHEL where we have hundreds of upstreams we are not
directly involved in) which is obviously different for OpenStack since
we have Russell, but it is very helpful if SRT is notified as early as
possible since we'll need to handle the security issues any ways at
some point..

- -- 
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJQvjAMAAoJEBYNRVNeJnmTmPwQAJx3WKrc3OHSkyjBukqt+x/V
6G3by9ZQZeUYnXPzKCW5uLC+nypea2zx/AKn6/QBwjcE+jTWzvI4EOkv6wpzxyC1
cdcRE1gLoaStPZhEfBAugjXwBMH8zwDE6htuEDZrazPNgSfOGYr7UAsr1KOh0dy+
ijY7fd1nJgakKl/LMrqbTRx0soh6ZFvQdZ51DEywDohs2Fn6CEeDiSbaj/4uUDGl
5s/4HM9CyfRF8fc8lFloU10QIdx+0E2kY+wMrFjfGUSX9UWtqKzj3HjE8mCIJzBq
RDOlKF0NSb3etasbYV881MPA0Ur9AYB5F03qoQvfRg0NWa3Mzuqty/CztYCg3Xii
UpGLhmPxX67dItotYr1uTnP7lTLieAjVbu6HOAPUcXVw1zvF3p0dDlhEn1Rsg0I3
FKMMyMUAeuObPeFhnnvRfnsRfQh45drDFGwv1v38lnFbXQyZTu9Yk9ysDekNJLvS
VyC8ZTGBizlyKbpJf2ABUF8kI2fS9jfUBkWtRxErnzElUmGPsMZ4yRPGYdRuMY49
0IrE4TcdWszAgZxaVRSj2CE2Dw8x1V1/ZUSUW5fyRKPOmZhtAuY2NRXYxk3NNeO/
5c6TQwnGec9GTmUMIFfWoUBCBORbib0d2Q3evQZ9MmO1VJEnSirXhIUt9LXq+9/C
60oOnghV/Ry4U+jzf6NX
=1lL1
-END PGP SIGNATURE-

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

Re: [Openstack] Understanding "flavors" of VM

[Marco CONSONNI]

Sorry, the directory you need to check is  /var/lib/nova/instances.

MCo.

On Tue, Dec 4, 2012 at 5:54 PM, Marco CONSONNI  wrote:

> Hi Ahmed,
>
> very technical questions.
> I'm not sure my answers are right: I'm just an user...
>
> In order to answer, I've just look at what happens and made some guess.
> Feel free to verify yourself.
>
> I'm assuming you are using KVM as I'm doing.
>
> The space for the boot disk and the ephemeral disk should be represented
> as files in the physical node where the VM is hosted.
> In order to check that, go to directory  /var/lib/nova on the node where
> the VM is running.
> As far as I understand, this is where nova (and KVM) keep the running
> instances' information.
> You should see a directory for each running instance named as
> instance-xxx, where xxx uniquely identifies an instance (there are
> several ways for uniquely identify an instance, this is one of many... but
> this is a different story).
> Go into one of these and check what you find.
>
> For what concerns nova-scheduler, I don't know what exactly does. I'm
> afraid that you need to test and see what happens.
>
> A nova command can help for inspecting what a node is using, in terms of
> resources.
>
> At the controller node (or any other node where you installed nova
> client), type the following command substituting OpenStack02 with the name
> of the node you want to inspect:
>
> *$ nova host-describe OpenStack02*
>
>
> +-+--+-+---+-+
>
> | HOST| PROJECT  | cpu | memory_mb |
> disk_gb |
>
>
> +-+--+-+---+-+
>
> | OpenStack02 | (total)  | 16  | 24101 | 90
> |
>
> | OpenStack02 | (used_max)   | 13  | 7680  | 0
> |
>
> | OpenStack02 | (used_now)   | 13  | 8192  | 0
> |
>
> | OpenStack02 | 456ec9d355ae4feebe48a2e79e703225 | 4   | 2048  | 0
> |
>
> | OpenStack02 | fb434e07b687494bb669fde23f497970 | 9   | 5632  | 0
> |
>
>
> +-+--+-+---+-+
>
> It return a brief report of the resources currently used by a node.
>
> To my knowledge,  the dashboard does not provide a similar page, at the
> time being.
>
> Hope it helps,
> Marco.
>
>
>
>
> On Tue, Dec 4, 2012 at 4:40 PM, Ahmed Al-Mehdi wrote:
>
>> Hi Marco,
>>
>> Thank you very much for the info, much much clearer.  I was looking for
>> the boot disk using "ls -l /dev/sd*", but the existence of /dev/vda1
>> should have given me a clue.
>>
>> A few follow up questions:
>>
>> - I am assuming the space for the VM boot disk is allocated from the
>> local hard disk of the physical host on which the VM is instantiated,
>> right?
>> - If Yes
>>- How is the boot disk represented on the physical host.  Is it a file
>> on the local filesystem that represent the VM boot disk?
>>- I am guessing there is some logic in nova-scheduler that checs
>> first if there is enough disk apace on the physical host for the VM(along 
>> with RAM,
>> VCPUs) before launching the VM on the host?
>>- Is there any way to find out from Horizon how much disk space is
>> available on a (or each) physical host for VM boot disk allocation?
>>
>> Thank you,
>> Ahmed.
>>
>>
>>
>>
>> On Tue, Dec 4, 2012 at 12:07 AM, Marco CONSONNI wrote:
>>
>>> Hello,
>>>
>>>
>>> When you use a flavor with an ephemeral disk size different from zero,
>>> the instance is booted with an extra virtual disk whose size is indicated
>>> by the ephemeral value (in GB).
>>>
>>> Using cirros image, try a flavor with ephemeral disk size different from
>>> zero (you need to create one yourself because the "standard" flavors have
>>> ephemeral size equal to 0), then log into the just booted instance and type:
>>>
>>>
>>> *$ ls /dev/vd**
>>>
>>> /dev/vda   /dev/vda1  /dev/vdb
>>>
>>>
>>>
>>> Disk /dev/vdb is a (virtual) disk, automatically created at boot time,
>>> corresponding to the ephemeral disk space indicated by the flavor . Please
>>> note that /dev/vda, mounted as /dev/vda1, is the boot disk, always created
>>> when you boot an instance.
>>>
>>> Verify the size of the available disks; more specifically, verify
>>> /dev/vdb:
>>>
>>> *
>>> *
>>>
>>> *$ sudo fdisk -l*
>>>
>>> Disk /dev/vda: 1073 MB, 1073741824 bytes
>>>
>>> 255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
>>>
>>> Units = sectors of 1 * 512 = 512 bytes
>>>
>>> Sector size (logical/physical): 512 bytes / 512 bytes
>>>
>>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>>
>>> Disk identifier: 0x
>>>
>>>
>>>
>>>Device Boot  Start End  Blocks   Id  System
>>>
>>> /dev/vda1   *   16065 2088449 1036192+  83  Linux
>>>
>>>
>>>
>>> Disk /dev/vdb: 1073 MB, 1073741824 bytes
>>>
>>> 16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
>>>
>>> Units = sectors of 1 * 512 = 512 by

Re: [Openstack] Understanding "flavors" of VM

[Marco CONSONNI]

Hi Ahmed,

very technical questions.
I'm not sure my answers are right: I'm just an user...

In order to answer, I've just look at what happens and made some guess.
Feel free to verify yourself.

I'm assuming you are using KVM as I'm doing.

The space for the boot disk and the ephemeral disk should be represented as
files in the physical node where the VM is hosted.
In order to check that, go to directory  /var/lib/nova on the node where
the VM is running.
As far as I understand, this is where nova (and KVM) keep the running
instances' information.
You should see a directory for each running instance named as
instance-xxx, where xxx uniquely identifies an instance (there are
several ways for uniquely identify an instance, this is one of many... but
this is a different story).
Go into one of these and check what you find.

For what concerns nova-scheduler, I don't know what exactly does. I'm
afraid that you need to test and see what happens.

A nova command can help for inspecting what a node is using, in terms of
resources.

At the controller node (or any other node where you installed nova client),
type the following command substituting OpenStack02 with the name of the
node you want to inspect:

*$ nova host-describe OpenStack02*

+-+--+-+---+-+

| HOST| PROJECT  | cpu | memory_mb |
disk_gb |

+-+--+-+---+-+

| OpenStack02 | (total)  | 16  | 24101 | 90
|

| OpenStack02 | (used_max)   | 13  | 7680  | 0
|

| OpenStack02 | (used_now)   | 13  | 8192  | 0
|

| OpenStack02 | 456ec9d355ae4feebe48a2e79e703225 | 4   | 2048  | 0
|

| OpenStack02 | fb434e07b687494bb669fde23f497970 | 9   | 5632  | 0
|

+-+--+-+---+-+

It return a brief report of the resources currently used by a node.

To my knowledge,  the dashboard does not provide a similar page, at the
time being.

Hope it helps,
Marco.



On Tue, Dec 4, 2012 at 4:40 PM, Ahmed Al-Mehdi wrote:

> Hi Marco,
>
> Thank you very much for the info, much much clearer.  I was looking for
> the boot disk using "ls -l /dev/sd*", but the existence of /dev/vda1
> should have given me a clue.
>
> A few follow up questions:
>
> - I am assuming the space for the VM boot disk is allocated from the
> local hard disk of the physical host on which the VM is instantiated,
> right?
> - If Yes
>- How is the boot disk represented on the physical host.  Is it a file
> on the local filesystem that represent the VM boot disk?
>- I am guessing there is some logic in nova-scheduler that checs
> first if there is enough disk apace on the physical host for the VM(along 
> with RAM,
> VCPUs) before launching the VM on the host?
>- Is there any way to find out from Horizon how much disk space is
> available on a (or each) physical host for VM boot disk allocation?
>
> Thank you,
> Ahmed.
>
>
>
>
> On Tue, Dec 4, 2012 at 12:07 AM, Marco CONSONNI wrote:
>
>> Hello,
>>
>>
>> When you use a flavor with an ephemeral disk size different from zero,
>> the instance is booted with an extra virtual disk whose size is indicated
>> by the ephemeral value (in GB).
>>
>> Using cirros image, try a flavor with ephemeral disk size different from
>> zero (you need to create one yourself because the "standard" flavors have
>> ephemeral size equal to 0), then log into the just booted instance and type:
>>
>>
>> *$ ls /dev/vd**
>>
>> /dev/vda   /dev/vda1  /dev/vdb
>>
>>
>>
>> Disk /dev/vdb is a (virtual) disk, automatically created at boot time,
>> corresponding to the ephemeral disk space indicated by the flavor . Please
>> note that /dev/vda, mounted as /dev/vda1, is the boot disk, always created
>> when you boot an instance.
>>
>> Verify the size of the available disks; more specifically, verify
>> /dev/vdb:
>>
>> *
>> *
>>
>> *$ sudo fdisk -l*
>>
>> Disk /dev/vda: 1073 MB, 1073741824 bytes
>>
>> 255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
>>
>> Units = sectors of 1 * 512 = 512 bytes
>>
>> Sector size (logical/physical): 512 bytes / 512 bytes
>>
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>
>> Disk identifier: 0x
>>
>>
>>
>>Device Boot  Start End  Blocks   Id  System
>>
>> /dev/vda1   *   16065 2088449 1036192+  83  Linux
>>
>>
>>
>> Disk /dev/vdb: 1073 MB, 1073741824 bytes
>>
>> 16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
>>
>> Units = sectors of 1 * 512 = 512 bytes
>>
>> Sector size (logical/physical): 512 bytes / 512 bytes
>>
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>>
>> Disk identifier: 0x
>>
>>
>>
>> Disk /dev/vdb doesn't contain a valid partition table
>>
>>
>>
>> Please note that /dev/vdb is made available as raw device, meaning that
>> you need to partition and format 

Re: [Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Gui Maluf]

I've change the default_store to file on glance-api.conf
even after changin this I'm getting the same error related to swift!


On Tue, Dec 4, 2012 at 1:45 PM, Razique Mahroua
wrote:

> Oh my bad, I misread.
> Let us know how it's going with Andrew's tip :)
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 4 déc. 2012 à 16:22, Gui Maluf  a écrit :
>
>
>
>
> On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua  > wrote:
>
>>
>> *Razique Mahroua** - **Nuage & Co*
>>  razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>> 
>>
>> Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :
>>
>> Hy, I've a ubuntu 12.04 cloud controller + node runing essex in
>> multi_node mode.
>> So I'm trying to install a new node but without success.
>>
>> Node and controller have the same /etc/network/interface/;
>>
>> You mean they both have the same IP address ?
>>
>  Course not. All machines have different IP.
>
>>
>> Node is running nova-{api-metadata,compute,network,volume};
>> nova.conf: http://paste.openstack.org/show/27390/
>> Node have this line above  uncommented and --my_ip changed
>> --enabled_apis=ec2,osapi_compute,osapi_volume,metadata
>>
>> Here is the nova-compute.log: http://paste.openstack.org/show/27387/with 
>> complete error.
>>
>> I'm trying to install two nodes, and from both I can reach all services
>> on cloud-controller.
>> telnet cloud-controller 9292 works from both nodes. They all have the
>> same nova.conf. I dont know what else can be this error.
>> I've check many things and I cant find a solution to this.
>> Thanks in advance!
>>
>> --
>> *guilherme* \n
>> \t *maluf*
>>
>>
>> Is keystone running ?
>> What $ keystone user-list shows ?
>>
> the whole cloud-controller-node works fine. keystone, vm, network, volume.
> The step of adding nodes is not working! I'm trying to remember anything
> I'd done. And the only think I can remeber is that I've changed the
> hostname of the CC-node.
> I dont know how this can affect the whole system and wherelse get more
> info about this issue!
>
>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> Regards,
>> Razique
>>
>>
>
>
> --
> *guilherme* \n
> \t *maluf*
>
>
>


-- 
*guilherme* \n
\t *maluf*
<>___
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] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Razique Mahroua]

Oh my bad, I misread.Let us know how it's going with Andrew's tip :)
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 4 déc. 2012 à 16:22, Gui Maluf  a écrit :On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua  wrote:


Razique Mahroua - Nuage & Co

razique.mahr...@gmail.comTel : +33 9 72 37 94 15



Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node mode.

So I'm trying to install a new node but without success.Node and controller have the same /etc/network/interface/; You mean they both have the same IP address ?

Course not. All machines have different IP.

Node is running nova-{api-metadata,compute,network,volume};

nova.conf: http://paste.openstack.org/show/27390/Node have this line above  uncommented and --my_ip changed--enabled_apis=ec2,osapi_compute,osapi_volume,metadata



Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with complete error.I'm trying to install two nodes, and from both I can reach all services on cloud-controller.



telnet cloud-controller 9292 works from both nodes. They all have the same nova.conf. I dont know what else can be this error.I've check many things and I cant find a solution to this.Thanks in advance!



-- guilherme \n\t malufIs keystone running ? What $ keystone user-list shows ?

the whole cloud-controller-node works fine. keystone, vm, network, volume. The step of adding nodes is not working! I'm trying to remember anything I'd done. And the only think I can remeber is that I've changed the hostname of the CC-node.

I dont know how this can affect the whole system and wherelse get more info about this issue! 


___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp

Regards,Razique-- guilherme \n\t maluf



___
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] Understanding "flavors" of VM

[Ahmed Al-Mehdi]

Hi Marco,

Thank you very much for the info, much much clearer.  I was looking for the
boot disk using "ls -l /dev/sd*", but the existence of /dev/vda1 should
have given me a clue.

A few follow up questions:

- I am assuming the space for the VM boot disk is allocated from the local
hard disk of the physical host on which the VM is instantiated, right?
- If Yes
   - How is the boot disk represented on the physical host.  Is it a file
on the local filesystem that represent the VM boot disk?
   - I am guessing there is some logic in nova-scheduler that checs
first if there is enough disk apace on the physical host for the VM (along
with RAM, VCPUs) before launching the VM on the host?
   - Is there any way to find out from Horizon how much disk space is
available on a (or each) physical host for VM boot disk allocation?

Thank you,
Ahmed.




On Tue, Dec 4, 2012 at 12:07 AM, Marco CONSONNI  wrote:

> Hello,
>
>
> When you use a flavor with an ephemeral disk size different from zero, the
> instance is booted with an extra virtual disk whose size is indicated by
> the ephemeral value (in GB).
>
> Using cirros image, try a flavor with ephemeral disk size different from
> zero (you need to create one yourself because the "standard" flavors have
> ephemeral size equal to 0), then log into the just booted instance and type:
>
>
> *$ ls /dev/vd**
>
> /dev/vda   /dev/vda1  /dev/vdb
>
>
>
> Disk /dev/vdb is a (virtual) disk, automatically created at boot time,
> corresponding to the ephemeral disk space indicated by the flavor . Please
> note that /dev/vda, mounted as /dev/vda1, is the boot disk, always created
> when you boot an instance.
>
> Verify the size of the available disks; more specifically, verify /dev/vdb:
>
> *
> *
>
> *$ sudo fdisk -l*
>
> Disk /dev/vda: 1073 MB, 1073741824 bytes
>
> 255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors
>
> Units = sectors of 1 * 512 = 512 bytes
>
> Sector size (logical/physical): 512 bytes / 512 bytes
>
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Disk identifier: 0x
>
>
>
>Device Boot  Start End  Blocks   Id  System
>
> /dev/vda1   *   16065 2088449 1036192+  83  Linux
>
>
>
> Disk /dev/vdb: 1073 MB, 1073741824 bytes
>
> 16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors
>
> Units = sectors of 1 * 512 = 512 bytes
>
> Sector size (logical/physical): 512 bytes / 512 bytes
>
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Disk identifier: 0x
>
>
>
> Disk /dev/vdb doesn't contain a valid partition table
>
>
>
> Please note that /dev/vdb is made available as raw device, meaning that
> you need to partition and format it before using.
>
> You can find instructions on how to do that here
> http://docs.openstack.org/folsom/openstack-compute/admin/content/configure-nova-volume.html(search
>  for command fdisk)
>
> Also note that this disk, being ephemeral, disappears when you terminate
> the VM. If you want to keep the data you produce with a VM that is destined
> to be terminated, you need to use Volumes that you explicitly create and
> attach using the services implemented by Cinder (former nova-volume).
>
>
> For what concerns the size you define for the boot disk, try and lunch two
> instances: one with flavor m1.tiny the other with m1.small:
>
>
> -- tiny --
>
> *$ sudo fdisk -l
> *
> Disk /dev/vda: 41 MB, 41126400 bytes
> 255 heads, 63 sectors/track, 5 cylinders, total 80325 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
>
>Device Boot  Start End  Blocks   Id  System
> /dev/vda1   *   16065   80324   32130   83  Linux
>
>
> -- small --
>
>
> *$ sudo fdisk -l
> *
> Disk /dev/vda: 21.5 GB, 21474836480 bytes
> 255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
>
>Device Boot  Start End  Blocks   Id  System
> /dev/vda1   *   160654192964920956792+  83  Linux
>
>
> As you notice, the size indicated by the flavor has effects on the size of
> the boot disk.
>
>
> Hope it helps,
> Marco.
>
>
>
>
> On Mon, Dec 3, 2012 at 7:03 PM, Ahmed Al-Mehdi wrote:
>
>> Hello,
>>
>> I instantiated a VM using the cirros image, using the pre-defined
>> "m1.small" (1 VCPU, 2 GB Ram, 20G boot disk, 0 Ephemeral disk).  I then
>> logged into the console of the VM to view some system stats.  The num of
>> CPU and memory makes sense, but I am a bit confused on the storage aspect.
>>  I see the output of "df -h " as following:
>>
>> $ df -h
>> Filesystem  Size UsedAvailable  Use%
>> Mounted on
>> /dev  1001.1M  0  1001.1M
>> 0% /d

Re: [Openstack] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Gui Maluf]

You're misundertanding me.
I've a cloud-controller-node that allready works. It runs many VMs, with
network working, distinct tenants and users, etc.
What I did was install a new bare metal server, install
nova-{compute,volume, network, api-metadata} and copy the
/etc/nova/nova.conf, change the my_ip option and uncomment the enabled_api
lines.
All services are :) on nova-manage service list.


Hm, good tip Andrew. I think you pointed out the correct think. My swift
endpoint is 127.0.0.1 ! Maybe this is causing the problem!

I'll change the endpoint and check if works!


On Tue, Dec 4, 2012 at 1:27 PM, Razique Mahroua
wrote:

> How did you proceed for installing that new node based on the controller ?
> You cloned the system  and renamed the server ?
> It can affects it in many ways, maybe /etc/hosts
> Did you updated all the openstack configuration files  ?
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 4 déc. 2012 à 16:22, Gui Maluf  a écrit :
>
>
>
>
> On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua  > wrote:
>
>>
>> *Razique Mahroua** - **Nuage & Co*
>>  razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>> 
>>
>> Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :
>>
>> Hy, I've a ubuntu 12.04 cloud controller + node runing essex in
>> multi_node mode.
>> So I'm trying to install a new node but without success.
>>
>> Node and controller have the same /etc/network/interface/;
>>
>> You mean they both have the same IP address ?
>>
>  Course not. All machines have different IP.
>
>>
>> Node is running nova-{api-metadata,compute,network,volume};
>> nova.conf: http://paste.openstack.org/show/27390/
>> Node have this line above  uncommented and --my_ip changed
>> --enabled_apis=ec2,osapi_compute,osapi_volume,metadata
>>
>> Here is the nova-compute.log: http://paste.openstack.org/show/27387/with 
>> complete error.
>>
>> I'm trying to install two nodes, and from both I can reach all services
>> on cloud-controller.
>> telnet cloud-controller 9292 works from both nodes. They all have the
>> same nova.conf. I dont know what else can be this error.
>> I've check many things and I cant find a solution to this.
>> Thanks in advance!
>>
>> --
>> *guilherme* \n
>> \t *maluf*
>>
>>
>> Is keystone running ?
>> What $ keystone user-list shows ?
>>
> the whole cloud-controller-node works fine. keystone, vm, network, volume.
> The step of adding nodes is not working! I'm trying to remember anything
> I'd done. And the only think I can remeber is that I've changed the
> hostname of the CC-node.
> I dont know how this can affect the whole system and wherelse get more
> info about this issue!
>
>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> Regards,
>> Razique
>>
>>
>
>
> --
> *guilherme* \n
> \t *maluf*
>
>
>


-- 
*guilherme* \n
\t *maluf*
<>___
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] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Razique Mahroua]

How did you proceed for installing that new node based on the controller ? You cloned the system  and renamed the server ?It can affects it in many ways, maybe /etc/hostsDid you updated all the openstack configuration files  ?
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 4 déc. 2012 à 16:22, Gui Maluf  a écrit :On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua  wrote:


Razique Mahroua - Nuage & Co

razique.mahr...@gmail.comTel : +33 9 72 37 94 15



Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node mode.

So I'm trying to install a new node but without success.Node and controller have the same /etc/network/interface/; You mean they both have the same IP address ?

Course not. All machines have different IP.

Node is running nova-{api-metadata,compute,network,volume};

nova.conf: http://paste.openstack.org/show/27390/Node have this line above  uncommented and --my_ip changed--enabled_apis=ec2,osapi_compute,osapi_volume,metadata



Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with complete error.I'm trying to install two nodes, and from both I can reach all services on cloud-controller.



telnet cloud-controller 9292 works from both nodes. They all have the same nova.conf. I dont know what else can be this error.I've check many things and I cant find a solution to this.Thanks in advance!



-- guilherme \n\t malufIs keystone running ? What $ keystone user-list shows ?

the whole cloud-controller-node works fine. keystone, vm, network, volume. The step of adding nodes is not working! I'm trying to remember anything I'd done. And the only think I can remeber is that I've changed the hostname of the CC-node.

I dont know how this can affect the whole system and wherelse get more info about this issue! 


___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp

Regards,Razique-- guilherme \n\t maluf



___
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] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Gui Maluf]

On Tue, Dec 4, 2012 at 1:16 PM, Razique Mahroua
wrote:

>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :
>
> Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node
> mode.
> So I'm trying to install a new node but without success.
>
> Node and controller have the same /etc/network/interface/;
>
> You mean they both have the same IP address ?
>
Course not. All machines have different IP.

>
> Node is running nova-{api-metadata,compute,network,volume};
> nova.conf: http://paste.openstack.org/show/27390/
> Node have this line above  uncommented and --my_ip changed
> --enabled_apis=ec2,osapi_compute,osapi_volume,metadata
>
> Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with
> complete error.
>
> I'm trying to install two nodes, and from both I can reach all services on
> cloud-controller.
> telnet cloud-controller 9292 works from both nodes. They all have the same
> nova.conf. I dont know what else can be this error.
> I've check many things and I cant find a solution to this.
> Thanks in advance!
>
> --
> *guilherme* \n
> \t *maluf*
>
>
> Is keystone running ?
> What $ keystone user-list shows ?
>
the whole cloud-controller-node works fine. keystone, vm, network, volume.
The step of adding nodes is not working! I'm trying to remember anything
I'd done. And the only think I can remeber is that I've changed the
hostname of the CC-node.
I dont know how this can affect the whole system and wherelse get more info
about this issue!


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


-- 
*guilherme* \n
\t *maluf*
<>___
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] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Razique Mahroua]

Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 4 déc. 2012 à 16:01, Gui Maluf  a écrit :Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node mode.So I'm trying to install a new node but without success.Node and controller have the same /etc/network/interface/; You mean they both have the same IP address ?Node is running nova-{api-metadata,compute,network,volume};

nova.conf: http://paste.openstack.org/show/27390/Node have this line above  uncommented and --my_ip changed--enabled_apis=ec2,osapi_compute,osapi_volume,metadata

Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with complete error.I'm trying to install two nodes, and from both I can reach all services on cloud-controller.

telnet cloud-controller 9292 works from both nodes. They all have the same nova.conf. I dont know what else can be this error.I've check many things and I cant find a solution to this.Thanks in advance!

-- guilherme \n\t malufIs keystone running ? What $ keystone user-list shows ?
___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelpRegards,Razique___
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] 500 Internal Server error and [Errno 113] EHOSTUNREACH when adding a new node

[Gui Maluf]

Hy, I've a ubuntu 12.04 cloud controller + node runing essex in multi_node
mode.
So I'm trying to install a new node but without success.

Node and controller have the same /etc/network/interface/;
Node is running nova-{api-metadata,compute,network,volume};
nova.conf: http://paste.openstack.org/show/27390/
Node have this line above  uncommented and --my_ip changed
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata

Here is the nova-compute.log: http://paste.openstack.org/show/27387/ with
complete error.

I'm trying to install two nodes, and from both I can reach all services on
cloud-controller.
telnet cloud-controller 9292 works from both nodes. They all have the same
nova.conf. I dont know what else can be this error.
I've check many things and I cant find a solution to this.
Thanks in advance!

-- 
*guilherme* \n
\t *maluf*
___
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] Blueprint proposal: Drop setuptools_git for including data/config files

[Thierry Carrez]

Sascha Peilicke wrote:
> Currently, the majority of OpenStack components make use of the
> Python module "setuptools_git" in order to install additional
> configuration files. This is basically the same functionality that
> the MANIFEST.in file (setuptools/distribute) provides, but
> automatic.

Note: This is a development topic, it should (have) be(en) posted to
openstack-dev to reach the appropriate audience. Please follow-up there.

> However, we recently discovered that this approach has issues from
> a packaging perspective. We weren't getting all the data/config
> files that the python package usually gets even though we were
> running the same commands:
> 
> $ python setup.py build
> 
> followed by:
> 
> $ python setup.py install --skip-build
> 
> We are building RPM packages from release tarballs (such as [1]),
> which of course don't include the .git directory. Therefore the
> setuptools_git approach can't do its magic, thus our package builds
> get wrong results. Having OpenStack components rely on
> setuptools_git at build time means we have to distribute the whole
> git repository along with the source code tarball. Of course this
> makes no sense, since it would increase the size of release
> tarballs dramatically and won't get shipped in distributions
> anyway.Therefore, we (and potentially other distribution vendors)
> would have to track these files manually in our RPM spec files. 
> Some reviews have already been opened on the topic (admittedly
> before we discovered the real issue). Given the different outcome
> of each review it seems that not everybody is aware that
> setuptools_git is used or of what it does.
> 
> https://review.openstack.org/#/c/17122/ (ceilometer) - this one
> got accepted before we knew what was going on
> 
> https://review.openstack.org/#/c/17347/ (cinder) - abandoned until
> the situation is clarified
> 
> https://review.openstack.org/#/c/17355/ (nova) - rejected
> 
> So the better solution would be to stop using setuptools_git and
> just include all the data/config files that are meant to be
> distributed in the MANIFEST.in file. This is what every Python
> developer should know about and has the benefit of increased
> transparency about what gets installed and what not. We created a
> blueprint to track this [2].
> 
> Thoughts?

A bit of history here:

We used to rely on MANIFEST.in to list all files, but people routinely
forgot to add new files to it. Apparently "every Python developer"
doesn't know (or care) about this. The end result was that we
discovered very late (sometimes after the release itself) that we
built incomplete tarballs. As a quick search[1] shows, I have
personally filed 27 bugs so far on the subject, so it's not a corner case.

[1] http://bit.ly/TDim7U

Relying on setuptools_git instead allows to avoid that issue
altogether. The projects that adopted it became a non-issue. The
projects that didn't adopt it yet are still a problem. I was about to
push setuptools_git support to projects that don't use it yet.

In summary, I would hate it if we went back to the previous situation.
I'm not personally attached to setuptools_git, but any proposed
replacement solution should keep its simplicity.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

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

[Openstack] Blueprint proposal: Drop setuptools_git for including data/config files

[Sascha Peilicke]

Currently, the majority of OpenStack components make use of the Python
module "setuptools_git" in order to install additional configuration
files. This is basically the same functionality that the MANIFEST.in
file (setuptools/distribute) provides, but automatic. However, we
recently discovered that this approach has issues from a packaging
perspective. We weren't getting all the data/config files that the
python package usually gets even though we were running the same commands:

$ python setup.py build

followed by:

$ python setup.py install --skip-build

We are building RPM packages from release tarballs (such as [1]), which
of course don't include the .git directory. Therefore the setuptools_git
approach can't do its magic, thus our package builds get wrong results.
Having OpenStack components rely on setuptools_git at build time means
we have to distribute the whole git repository along with the source
code tarball. Of course this makes no sense, since it would increase the
size of release tarballs dramatically and won't get shipped in
distributions anyway.Therefore, we (and potentially other distribution
vendors) would have to track these files manually in our RPM spec files.
Some reviews have already been opened on the topic (admittedly before we
discovered the real issue). Given the different outcome of each review
it seems that not everybody is aware that setuptools_git is used or of
what it does.

https://review.openstack.org/#/c/17122/ (ceilometer) - this one got
accepted before we knew what was going on

https://review.openstack.org/#/c/17347/ (cinder) - abandoned until the
situation is clarified

https://review.openstack.org/#/c/17355/ (nova) - rejected

So the better solution would be to stop using setuptools_git and just
include all the data/config files that are meant to be distributed in
the MANIFEST.in file. This is what every Python developer should know
about and has the benefit of increased transparency about what gets
installed and what not. We created a blueprint to track this [2].

Thoughts?

Footnotes:
 [1]
https://launchpad.net/cinder/grizzly/grizzly-1/+download/cinder-2013.1%7Eg1.tar.gz
 [2] https://blueprints.launchpad.net/nova/+spec/drop-setuptools-git
-- 
With kind regards,
Sascha Peilicke
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] How to deploy openstack automatically in your env.

[Choe, Cheng-Dae]

if you deploy with chef. It's a good starting point

- https://github.com/rcbops-cookbooks
- https://github.com/whitekid/openstack-chef

2012. 12. 4., 오후 8:58, Derek Higgins  작성:

> On 12/04/2012 11:52 AM, Lei Zhang wrote:
>> Hi Tim,
>> 
>> The module you are using is puppetlabs-openstack? Or is wrote by
>> yourself? Here is the puppet openstack module dependency. I don't think
>> it supported RHEL
> Hi Lei,
>   I have been using the puppetlabs-openstack modules on RHEL, see here
> for a collection of the modules that I normally use
> https://github.com/derekhiggins/openstackpuppetmodules
> 
> thanks,
> Derek.
> 
>> 
>> |/etc/puppet/modules
>> └─┬ puppetlabs-openstack (v1.0.3)
>>  ├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
>>  ├─┬ puppetlabs-glance (v1.0.0)
>>  │ ├── cprice404-inifile (v0.9.0)
>>  │ └─┬ puppetlabs-keystone (v1.0.1)
>>  │   └─┬ puppetlabs-mysql (v0.5.0)
>>  │ └── puppetlabs-stdlib (v3.2.0)
>>  ├─┬ puppetlabs-horizon (v1.0.0)
>>  │ ├── saz-memcached (v2.0.4)
>>  │ └─┬ puppetlabs-apache (v0.5.0-rc1)
>>  │   └── puppetlabs-firewall (v0.0.4)
>>  └─┬ puppetlabs-nova (v1.0.1)
>>├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
>>├── puppetlabs-apt (v1.1.0)
>>├── puppet-cinder (v1.0.1)
>>├── puppetlabs-rabbitmq (v2.0.2)
>>└── duritong-sysctl (v0.0.1)|
>> 
>> 
>> 
>> On Mon, Dec 3, 2012 at 11:59 PM, Tim Bell > > wrote:
>> 
>>Lei,
>> 
>>At CERN, we run our RHEL-based OpenStack instance with the puppetlabs
>>modules. They work very well and simplify the multi-node deployments.
>> 
>>We've got around 200 hypervisors deployed with this method.
>> 
>>Tim
>> 
>>> -Original Message-
>>> From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
>>
>>> [mailto:openstack-bounces+tim.bell
>>=cern...@lists.launchpad.net
>>] On Behalf
>>Of
>>> Derek Higgins
>>> Sent: 03 December 2012 16:37
>>> To: Lei Zhang
>>> Cc: openstack@lists.launchpad.net
>>
>>> Subject: Re: [Openstack] How to deploy openstack automatically in your
>>env.
>>> 
>>> Hi Lei,
>>> 
>>> On 12/03/2012 09:15 AM, Lei Zhang wrote:
 Hi all,
 
 I search the internet for days and found several automatically tool.
 Including
 
  * devstack
  * puppet+pupet-openstack
  * stackops
  * OneStack
 
 But It seems that all the scripts are well tested on ubuntu not
>>RHEL.
 How could you guys to deploy the openstack automatically, especially
 on RHEL.
>>> 
>>>   a lot of work has gone into the puppetlabs puppet modules so
>>that they
>>work
>>> on RHEL,
>>> 
>>> you can download the modules from their github account
>>> https://github.com/puppetlabs/
>>> 
>>> alternatively, I have been working on a tool to deploy openstack
>>on RHEL
>>and
>>> Fedora, its still at early stages and probably a bit rough around the
>>edges but if
>>> your interested you can try it out https://github.com/fedora-
>>> openstack/packstack
>>> 
>>> currently you can use packstack to install folsom keystone,
>>glance, nova,
>>cinder,
>>> horizon and swift on Multiple RHEL or Fedora servers. If you want
>>to try
>>it out it
>>> would be great to get any feedback you have.
>>> 
>>> packstack uses the puppetlabs modules to apply puppet manifests to
>>individual
>>> servers without the requirement of having a puppet master server.
>>> 
>>> thanks,
>>> Derek.
>>> 
 
 --
 Lei Zhang
 
 Blog: http://jeffrey4l.github.com
 twitter/weibo: @jeffrey4l
 
 
 
 ___
 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
>> 
>> 
>> 
>> 
>> -- 
>> Lei Zhang
>> 
>> Blog: http://jeffrey4l.github.com
>> twitter/weibo: @jeffrey4l
>> 
> 
> 
> ___
> 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 deploy openstack automatically in your env.

[Derek Higgins]

On 12/04/2012 11:52 AM, Lei Zhang wrote:
> Hi Tim,
> 
> The module you are using is puppetlabs-openstack? Or is wrote by
> yourself? Here is the puppet openstack module dependency. I don't think
> it supported RHEL
Hi Lei,
   I have been using the puppetlabs-openstack modules on RHEL, see here
for a collection of the modules that I normally use
https://github.com/derekhiggins/openstackpuppetmodules

thanks,
Derek.

> 
> |/etc/puppet/modules
> └─┬ puppetlabs-openstack (v1.0.3)
>   ├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
>   ├─┬ puppetlabs-glance (v1.0.0)
>   │ ├── cprice404-inifile (v0.9.0)
>   │ └─┬ puppetlabs-keystone (v1.0.1)
>   │   └─┬ puppetlabs-mysql (v0.5.0)
>   │ └── puppetlabs-stdlib (v3.2.0)
>   ├─┬ puppetlabs-horizon (v1.0.0)
>   │ ├── saz-memcached (v2.0.4)
>   │ └─┬ puppetlabs-apache (v0.5.0-rc1)
>   │   └── puppetlabs-firewall (v0.0.4)
>   └─┬ puppetlabs-nova (v1.0.1)
> ├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
> ├── puppetlabs-apt (v1.1.0)
> ├── puppet-cinder (v1.0.1)
> ├── puppetlabs-rabbitmq (v2.0.2)
> └── duritong-sysctl (v0.0.1)|
> 
> 
> 
> On Mon, Dec 3, 2012 at 11:59 PM, Tim Bell  > wrote:
> 
> Lei,
> 
> At CERN, we run our RHEL-based OpenStack instance with the puppetlabs
> modules. They work very well and simplify the multi-node deployments.
> 
> We've got around 200 hypervisors deployed with this method.
> 
> Tim
> 
> > -Original Message-
> > From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
> 
> > [mailto:openstack-bounces+tim.bell
> =cern...@lists.launchpad.net
> ] On Behalf
> Of
> > Derek Higgins
> > Sent: 03 December 2012 16:37
> > To: Lei Zhang
> > Cc: openstack@lists.launchpad.net
> 
> > Subject: Re: [Openstack] How to deploy openstack automatically in your
> env.
> >
> > Hi Lei,
> >
> > On 12/03/2012 09:15 AM, Lei Zhang wrote:
> > > Hi all,
> > >
> > > I search the internet for days and found several automatically tool.
> > > Including
> > >
> > >   * devstack
> > >   * puppet+pupet-openstack
> > >   * stackops
> > >   * OneStack
> > >
> > > But It seems that all the scripts are well tested on ubuntu not
> RHEL.
> > > How could you guys to deploy the openstack automatically, especially
> > > on RHEL.
> >
> >a lot of work has gone into the puppetlabs puppet modules so
> that they
> work
> > on RHEL,
> >
> > you can download the modules from their github account
> > https://github.com/puppetlabs/
> >
> > alternatively, I have been working on a tool to deploy openstack
> on RHEL
> and
> > Fedora, its still at early stages and probably a bit rough around the
> edges but if
> > your interested you can try it out https://github.com/fedora-
> > openstack/packstack
> >
> > currently you can use packstack to install folsom keystone,
> glance, nova,
> cinder,
> > horizon and swift on Multiple RHEL or Fedora servers. If you want
> to try
> it out it
> > would be great to get any feedback you have.
> >
> > packstack uses the puppetlabs modules to apply puppet manifests to
> individual
> > servers without the requirement of having a puppet master server.
> >
> > thanks,
> > Derek.
> >
> > >
> > > --
> > > Lei Zhang
> > >
> > > Blog: http://jeffrey4l.github.com
> > > twitter/weibo: @jeffrey4l
> > >
> > >
> > >
> > > ___
> > > 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
> 
> 
> 
> 
> -- 
> Lei Zhang
> 
> Blog: http://jeffrey4l.github.com
> twitter/weibo: @jeffrey4l
> 


___
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 deploy openstack automatically in your env.

[Lei Zhang]

Hi Tim,

The module you are using is puppetlabs-openstack? Or is wrote by yourself?
Here is the puppet openstack module dependency. I don't think it supported
RHEL

/etc/puppet/modules
└─┬ puppetlabs-openstack (v1.0.3)
  ├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
  ├─┬ puppetlabs-glance (v1.0.0)
  │ ├── cprice404-inifile (v0.9.0)
  │ └─┬ puppetlabs-keystone (v1.0.1)
  │   └─┬ puppetlabs-mysql (v0.5.0)
  │ └── puppetlabs-stdlib (v3.2.0)
  ├─┬ puppetlabs-horizon (v1.0.0)
  │ ├── saz-memcached (v2.0.4)
  │ └─┬ puppetlabs-apache (v0.5.0-rc1)
  │   └── puppetlabs-firewall (v0.0.4)
  └─┬ puppetlabs-nova (v1.0.1)
├── UNMET DEPENDENCY puppetlabs-cinder (>= 1.0.1)
├── puppetlabs-apt (v1.1.0)
├── puppet-cinder (v1.0.1)
├── puppetlabs-rabbitmq (v2.0.2)
└── duritong-sysctl (v0.0.1)



On Mon, Dec 3, 2012 at 11:59 PM, Tim Bell  wrote:

> Lei,
>
> At CERN, we run our RHEL-based OpenStack instance with the puppetlabs
> modules. They work very well and simplify the multi-node deployments.
>
> We've got around 200 hypervisors deployed with this method.
>
> Tim
>
> > -Original Message-
> > From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
> > [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On
> Behalf
> Of
> > Derek Higgins
> > Sent: 03 December 2012 16:37
> > To: Lei Zhang
> > Cc: openstack@lists.launchpad.net
> > Subject: Re: [Openstack] How to deploy openstack automatically in your
> env.
> >
> > Hi Lei,
> >
> > On 12/03/2012 09:15 AM, Lei Zhang wrote:
> > > Hi all,
> > >
> > > I search the internet for days and found several automatically tool.
> > > Including
> > >
> > >   * devstack
> > >   * puppet+pupet-openstack
> > >   * stackops
> > >   * OneStack
> > >
> > > But It seems that all the scripts are well tested on ubuntu not RHEL.
> > > How could you guys to deploy the openstack automatically, especially
> > > on RHEL.
> >
> >a lot of work has gone into the puppetlabs puppet modules so that they
> work
> > on RHEL,
> >
> > you can download the modules from their github account
> > https://github.com/puppetlabs/
> >
> > alternatively, I have been working on a tool to deploy openstack on RHEL
> and
> > Fedora, its still at early stages and probably a bit rough around the
> edges but if
> > your interested you can try it out https://github.com/fedora-
> > openstack/packstack
> >
> > currently you can use packstack to install folsom keystone, glance, nova,
> cinder,
> > horizon and swift on Multiple RHEL or Fedora servers. If you want to try
> it out it
> > would be great to get any feedback you have.
> >
> > packstack uses the puppetlabs modules to apply puppet manifests to
> individual
> > servers without the requirement of having a puppet master server.
> >
> > thanks,
> > Derek.
> >
> > >
> > > --
> > > Lei Zhang
> > >
> > > Blog: http://jeffrey4l.github.com
> > > twitter/weibo: @jeffrey4l
> > >
> > >
> > >
> > > ___
> > > 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
>



-- 
Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l
___
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] config_drive doesn't create disk.config

[Jian Hua Geng]

Vish,

Many thanks for u comments, but as you know to support windows sysprep
image, we need save the unattend.xml in the CDROM or C:\ device. So, we
want to extend the config drive to attach a CDROM device when launch VM.

Anyway, I think attach a CDROM when launch new VM is a common requirement,
right?

--
Best regard,
David Geng
--


   
 Vishvananda   
 Ishaya
 Jian Hua Geng/China/IBM@IBMCN,  
cc
 12/04/2012 06:32  openstack@lists.launchpad.net   
 AMSubject
   Re: [Openstack] [openstack] 
   config_drive  doesn't
   create disk.config  
   
   
   
   
   
   





On Dec 2, 2012, at 6:15 PM, Jian Hua Geng  wrote:



  I saw the comments in the
  https://bugs.launchpad.net/nova/+bug/1029647 , can anyone give me
  more detail introduction of this decision about why the functionality
  for using an image id for config drive was removed?

  Just for example for our requirement: We want create a CDROM and
  write some information in it such as the sysprep info for windows
  when run vm.
  First we need extend the config drive to support both cdrom and file
  disk device, second we create an iso image in glance which is used to
  save the sysprep info and share with other user in cloud, then wen
  can use this config_drive_id to load the iso.
  Have any suggestion or solution for this requirement?


Here is one option that you could use. Create a volume instead of an image
(or create the volume from the image), snapshot the volume. If you pass the
volume snapshot in as a secondary drive in block_device_mapping on boot,
then you will get a volume copy of the image. If it is
delete_on_terminate=True then the volume will be deleted when you terminate
the vm.

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

Re: [Openstack] [Keystone] LDAP Backend for Catalog

[Dolph Mathews]

Neither have I.


-Dolph


On Mon, Dec 3, 2012 at 1:25 PM, heckj  wrote:

> I haven't heard any demand for it -
>
> - joe
>
> On Dec 3, 2012, at 11:13 AM, Adam Young  wrote:
> > Right now, only the Identity submodule has an LDAP backend.  This is
> user, tenants, and roles.  Is there any requirement for the Catalog to have
> an LDAP back end?  Endpoints and Services do not necessarily map directly
> to the LDAP view of machines, but could probably be made to fit.  I will
> start investigating the feasibility if there is any demand for it.
> >
> > ___
> > 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] How to deploy openstack automatically in your env.

[Staicu Gabriel]

Hi,

Also to get starting you can use openstack-demo-install which comes in the 
packet openstack-utils.

Regards,
Gabriel




 From: Lei Zhang 
To: Tim Bell  
Cc: "openstack@lists.launchpad.net"  
Sent: Tuesday, December 4, 2012 4:08 AM
Subject: Re: [Openstack] How to deploy openstack automatically in your env.
 

Thanks all guys. Finally, I will try the puppet on the RHEL today and check 
whether it works. 



On Mon, Dec 3, 2012 at 11:59 PM, Tim Bell  wrote:

Lei,
>
>At CERN, we run our RHEL-based OpenStack instance with the puppetlabs
>modules. They work very well and simplify the multi-node deployments.
>
>We've got around 200 hypervisors deployed with this method.
>
>Tim
>
>
>> -Original Message-
>> From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
>> [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf
>Of
>> Derek Higgins
>> Sent: 03 December 2012 16:37
>> To: Lei Zhang
>> Cc: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] How to deploy openstack automatically in your
>env.
>>
>> Hi Lei,
>>
>> On 12/03/2012 09:15 AM, Lei Zhang wrote:
>> > Hi all,
>> >
>> > I search the internet for days and found several automatically tool.
>> > Including
>> >
>> >   * devstack
>> >   * puppet+pupet-openstack
>> >   * stackops
>> >   * OneStack
>> >
>> > But It seems that all the scripts are well tested on ubuntu not RHEL.
>> > How could you guys to deploy the openstack automatically, especially
>> > on RHEL.
>>
>>    a lot of work has gone into the puppetlabs puppet modules so that they
>work
>> on RHEL,
>>
>> you can download the modules from their github account
>> https://github.com/puppetlabs/
>>
>> alternatively, I have been working on a tool to deploy openstack on RHEL
>and
>> Fedora, its still at early stages and probably a bit rough around the
>edges but if
>> your interested you can try it out https://github.com/fedora-
>> openstack/packstack
>>
>> currently you can use packstack to install folsom keystone, glance, nova,
>cinder,
>> horizon and swift on Multiple RHEL or Fedora servers. If you want to try
>it out it
>> would be great to get any feedback you have.
>>
>> packstack uses the puppetlabs modules to apply puppet manifests to
>individual
>> servers without the requirement of having a puppet master server.
>>
>> thanks,
>> Derek.
>>
>> >
>> > --
>> > Lei Zhang
>> >
>> > Blog: http://jeffrey4l.github.com
>> > twitter/weibo: @jeffrey4l
>> >
>> >
>> >
>> > ___
>> > 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
>


-- 

Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l

___
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] resizing instance fails

[Marco CONSONNI]

Not sure, but it seems like this feature is available for XenServer, only
http://osdir.com/ml/openstack-cloud-computing/2011-10/msg00473.html

Does anybody know more?

Marco.

On Mon, Dec 3, 2012 at 3:42 PM, Afef MDHAFFAR wrote:

> Hi all,
>
> when I try to resize a running instance, I get this error:
> Is there any way to solve it?
>
>
> 2012-12-03 14:38:25 ERROR nova.compute.manager
> [req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] [instance:
> d3dba21b-3877-4da3-a2ab-8128f8515573] VHD coalesce attempts exceeded (5),
> giving up Setting instance vm_state to ERROR
> 2012-12-03 14:38:25 DEBUG nova.manager [-] Running periodic task
> SchedulerManager._expire_reservations from (pid=19093) periodic_tasks
> /opt/stack/nova/nova/manager.py:171
> 2012-12-03 14:38:25 DEBUG nova.openstack.common.lockutils
> [req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore
> "compute_resources" for method "update_usage"... from (pid=19070) inner
> /opt/stack/nova/nova/openstack/common/lockutils.py:185
> 2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] received
> {u'_context_roles': [], u'_context_request_id':
> u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb', u'_context_quota_class': None,
> u'_context_project_name': None, u'_context_service_catalog': None,
> u'_context_user_name': None, u'_context_auth_token': '',
> u'args': {u'service_name': u'compute', u'host': u'computeDomU03',
> u'capabilities': {u'host_name-description': u'Default install of
> XenServer', u'disk_available': 230087983104, u'host_hostname':
> u'compute09', u'supported_instances': [[u'x86_64', u'xapi', u'xen'],
> [u'x86_32p', u'xapi', u'xen'], [u'x86_32', u'xapi', u'hvm'], [u'x86_32p',
> u'xapi', u'hvm'], [u'x86_64', u'xapi', u'hvm']], u'host_memory_overhead':
> 106897408, u'enabled': u'true', u'host_ip': u'10.0.1.19',
> u'host_capabilities': [u'xen-3.0-x86_64', u'xen-3.0-x86_32p',
> u'hvm-3.0-x86_32', u'hvm-3.0-x86_32p', u'hvm-3.0-x86_64'], u'host_uuid':
> u'03433673-d30c-4f8e-94cc-43d53f9c2207', u'host_memory_free': 5261139968,
> u'disk_total': 242124587008, u'host_ip_address': u'10.0.1.166',
> u'hypervisor_hostname': u'compute09', u'host_memory_total': 8589463552,
> u'host_memory_free_computed': 5178503168, u'disk_used': 12036603904,
> u'host_other-config': {u'agent_start_time': u'1353496206.', u'boot_time':
> u'1353496188.', u'no_local_storage': u'true'}, u'host_name-label':
> u'compute09', u'host_cpu_info': {u'physical_features':
> u'---', u'modelname': u'Dual-Core AMD
> Opteron(tm) Processor 2216 HE', u'vendor': u'AuthenticAMD', u'features':
> u'---', u'family': 15, u'maskable': u'no',
> u'cpu_count': 4, u'flags': u'fpu de tsc msr pae cx8 apic cmov pat clflush
> mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good
> nopl extd_apicid pni cx16 hypervisor lahf_lm cmp_legacy extapic
> cr8_legacy', u'stepping': 2, u'model': 65, u'features_after_reboot':
> u'---', u'speed': u'2394.010'}}},
> u'_context_instance_lock_checked': False, u'_context_is_admin': True,
> u'version': u'2.0', u'_context_project_id': None, u'_context_timestamp':
> u'2012-12-03T14:38:26.342811', u'_context_read_deleted': u'no',
> u'_context_user_id': None, u'method': u'update_service_capabilities',
> u'_context_remote_address': None} from (pid=19093) _safe_log
> /opt/stack/nova/nova/openstack/common/rpc/common.py:195
> 2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] unpacked
> context: {'project_name': None, 'user_id': None, 'roles': [], 'timestamp':
> u'2012-12-03T14:38:26.342811', 'auth_token': '',
> 'remote_address': None, 'quota_class': None, 'is_admin': True,
> 'service_catalog': None, 'request_id':
> u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb', 'instance_lock_checked':
> False, 'project_id': None, 'user_name': None, 'read_deleted': u'no'} from
> (pid=19093) _safe_log
> /opt/stack/nova/nova/openstack/common/rpc/common.py:195
> 2012-12-03 14:38:26 DEBUG nova.scheduler.host_manager
> [req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb None None] Received compute
> service update from (u'computeDomU03', u'compute09'). from (pid=19093)
> update_service_capabilities
> /opt/stack/nova/nova/scheduler/host_manager.py:340
> 2012-12-03 14:38:26 DEBUG nova.openstack.common.lockutils
> [req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore
> "compute_resources" for method "update_usage"... from (pid=19070) inner
> /opt/stack/nova/nova/openstack/common/lockutils.py:185
> 2012-12-03 14:38:26 ERROR nova.openstack.common.rpc.amqp [-] Exception
> during message handling
> 2012-12-03 14:38:26 TRACE nova.openstack.common.rpc.amqp Traceback (most
> recent call last):
> 2012-12-03 14:38:26 TRACE nova.openstack.common.rpc.amqp   File
> "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 276, in
> _process_data
> 2012-12-03 14:38:26 TRACE nova.openstack.common.rpc.amqp rval =
> self.proxy.dispatch(ctxt, version, method, **arg

[Openstack] "glance image-list" command shows nothing

[Salman Riaz]

Hi,
I am a newbie in openstack.
I am following "openstack-install-guide-yum-folsom" guide to install this on 
CentOS Machine. I have currently installed Keystone Service and Glance Service. 
When I run "glance image-list" command after image creation steps, it shows 
nothing.
Can any one guide me in this regard.

Regards,
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

Re: [Openstack] Understanding "flavors" of VM

[Marco CONSONNI]

Hello,


When you use a flavor with an ephemeral disk size different from zero, the
instance is booted with an extra virtual disk whose size is indicated by
the ephemeral value (in GB).

Using cirros image, try a flavor with ephemeral disk size different from
zero (you need to create one yourself because the "standard" flavors have
ephemeral size equal to 0), then log into the just booted instance and type:


*$ ls /dev/vd**

/dev/vda   /dev/vda1  /dev/vdb



Disk /dev/vdb is a (virtual) disk, automatically created at boot time,
corresponding to the ephemeral disk space indicated by the flavor . Please
note that /dev/vda, mounted as /dev/vda1, is the boot disk, always created
when you boot an instance.

Verify the size of the available disks; more specifically, verify /dev/vdb:

*
*

*$ sudo fdisk -l*

Disk /dev/vda: 1073 MB, 1073741824 bytes

255 heads, 63 sectors/track, 130 cylinders, total 2097152 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x



   Device Boot  Start End  Blocks   Id  System

/dev/vda1   *   16065 2088449 1036192+  83  Linux



Disk /dev/vdb: 1073 MB, 1073741824 bytes

16 heads, 63 sectors/track, 2080 cylinders, total 2097152 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x



Disk /dev/vdb doesn't contain a valid partition table



Please note that /dev/vdb is made available as raw device, meaning that you
need to partition and format it before using.

You can find instructions on how to do that here
http://docs.openstack.org/folsom/openstack-compute/admin/content/configure-nova-volume.html(search
for command fdisk)

Also note that this disk, being ephemeral, disappears when you terminate
the VM. If you want to keep the data you produce with a VM that is destined
to be terminated, you need to use Volumes that you explicitly create and
attach using the services implemented by Cinder (former nova-volume).


For what concerns the size you define for the boot disk, try and lunch two
instances: one with flavor m1.tiny the other with m1.small:


-- tiny --

*$ sudo fdisk -l
*
Disk /dev/vda: 41 MB, 41126400 bytes
255 heads, 63 sectors/track, 5 cylinders, total 80325 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/vda1   *   16065   80324   32130   83  Linux


-- small --


*$ sudo fdisk -l
*
Disk /dev/vda: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/vda1   *   160654192964920956792+  83  Linux


As you notice, the size indicated by the flavor has effects on the size of
the boot disk.


Hope it helps,
Marco.



On Mon, Dec 3, 2012 at 7:03 PM, Ahmed Al-Mehdi wrote:

> Hello,
>
> I instantiated a VM using the cirros image, using the pre-defined
> "m1.small" (1 VCPU, 2 GB Ram, 20G boot disk, 0 Ephemeral disk).  I then
> logged into the console of the VM to view some system stats.  The num of
> CPU and memory makes sense, but I am a bit confused on the storage aspect.
>  I see the output of "df -h " as following:
>
> $ df -h
> Filesystem  Size UsedAvailable  Use%
>   Mounted on
> /dev  1001.1M  0  1001.1M
> 0% /dev
> /dev/vda1 23.2M12.9M   9.1M   59%
> /
> tmpfs1004.1M  0  1004.1M
> 0% /dev/shm
> tmpfs  200.0K20.0K180.0K   10%
> /run
>
>
> What is the difference between Boot disk and Ephemeral disk?
>
> How can I correlate the 20G boot disk to the output of "df -h".
>
>
> Regards,
> Ahmed.
>
>
> ___
> 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