[Openstack] Keystone API
Hi,
I'am working on enhancing keystone PublicAPI to support CORS.
Everything seem to work well except that Keystone is formatting
responses with Transfer-Encoding: chunked which isn't accepted for
OPTIONS query by browsers (chrome, firefox). Does anyone knows how to
force keystone API to use plain format ? My CorsController is as
follows:
class CorsController(wsgi.Application):
def __init__(self):
super(CorsController, self).__init__()
def get_options(self, context):
headers = [('Access-Control-Allow-Headers',
'origin,content-type,accept,x-auth-token')]
headers.append(('Access-Control-Allow-Methods', 'POST'))
headers.append(('Access-Control-Allow-Origin',
'https://178.239.138.10:8433'))
headers.append(('Access-Control-Max-Age', '60'))
headers.append(('Content-Length', '0'))
return wsgi.render_response(status=(200, 'OK'),
headers=headers)
Sample request:
echo -e 'OPTIONS /v2.0/tokens HTTP/1.1\r\n' | nc 10.76.0.119 5000
HTTP/1.1 200 OK
Access-Control-Allow-Headers: origin,content-type,accept,x-auth-token
Access-Control-Allow-Methods: POST
Access-Control-Allow-Origin: https://10.76.0.119:8433
Access-Control-Max-Age: 60
Date: Thu, 21 Jun 2012 16:52:33 GMT
Transfer-Encoding: chunked
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
___
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 API
I have created bug report:
https://bugs.launchpad.net/keystone/+bug/1016171
On Thu, Jun 21, 2012 at 6:57 PM, Tomasz Paszkowski ss7...@gmail.com wrote:
Hi,
I'am working on enhancing keystone PublicAPI to support CORS.
Everything seem to work well except that Keystone is formatting
responses with Transfer-Encoding: chunked which isn't accepted for
OPTIONS query by browsers (chrome, firefox). Does anyone knows how to
force keystone API to use plain format ? My CorsController is as
follows:
class CorsController(wsgi.Application):
def __init__(self):
super(CorsController, self).__init__()
def get_options(self, context):
headers = [('Access-Control-Allow-Headers',
'origin,content-type,accept,x-auth-token')]
headers.append(('Access-Control-Allow-Methods', 'POST'))
headers.append(('Access-Control-Allow-Origin',
'https://178.239.138.10:8433'))
headers.append(('Access-Control-Max-Age', '60'))
headers.append(('Content-Length', '0'))
return wsgi.render_response(status=(200, 'OK'),
headers=headers)
Sample request:
echo -e 'OPTIONS /v2.0/tokens HTTP/1.1\r\n' | nc 10.76.0.119 5000
HTTP/1.1 200 OK
Access-Control-Allow-Headers: origin,content-type,accept,x-auth-token
Access-Control-Allow-Methods: POST
Access-Control-Allow-Origin: https://10.76.0.119:8433
Access-Control-Max-Age: 60
Date: Thu, 21 Jun 2012 16:52:33 GMT
Transfer-Encoding: chunked
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
___
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 API
bingo :-) You're great !
On Thu, Jun 21, 2012 at 8:34 PM, Dolph Mathews dolph.math...@gmail.com wrote:
If you let webob calculate the Content-Length by itself it won't resort to
adding a Transfer-Encoding header:
https://review.openstack.org/#/c/8818
On Thu, Jun 21, 2012 at 12:54 PM, Tomasz Paszkowski ss7...@gmail.com
wrote:
I have created bug report:
https://bugs.launchpad.net/keystone/+bug/1016171
On Thu, Jun 21, 2012 at 6:57 PM, Tomasz Paszkowski ss7...@gmail.com
wrote:
Hi,
I'am working on enhancing keystone PublicAPI to support CORS.
Everything seem to work well except that Keystone is formatting
responses with Transfer-Encoding: chunked which isn't accepted for
OPTIONS query by browsers (chrome, firefox). Does anyone knows how to
force keystone API to use plain format ? My CorsController is as
follows:
class CorsController(wsgi.Application):
def __init__(self):
super(CorsController, self).__init__()
def get_options(self, context):
headers = [('Access-Control-Allow-Headers',
'origin,content-type,accept,x-auth-token')]
headers.append(('Access-Control-Allow-Methods', 'POST'))
headers.append(('Access-Control-Allow-Origin',
'https://178.239.138.10:8433'))
headers.append(('Access-Control-Max-Age', '60'))
headers.append(('Content-Length', '0'))
return wsgi.render_response(status=(200, 'OK'),
headers=headers)
Sample request:
echo -e 'OPTIONS /v2.0/tokens HTTP/1.1\r\n' | nc 10.76.0.119 5000
HTTP/1.1 200 OK
Access-Control-Allow-Headers: origin,content-type,accept,x-auth-token
Access-Control-Allow-Methods: POST
Access-Control-Allow-Origin: https://10.76.0.119:8433
Access-Control-Max-Age: 60
Date: Thu, 21 Jun 2012 16:52:33 GMT
Transfer-Encoding: chunked
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
___
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] [metering] nova volume notifications
Great, many thanks. I'am still using essex as development base, it's time to change. , On Sat, Jun 2, 2012 at 6:11 PM, Craig Vyvial cp16...@gmail.com wrote: Tomasz, There are volume notifications being sent by the volume manger now in trunk. This is not in the Essex release. Here is a list of all the notifications that are currently being emitted by the managers. http://wiki.openstack.org/SystemUsageData Hope this helps. Thanks, -Craig On Fri, Jun 1, 2012 at 1:02 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: The service that manages the volumes should send notifications. If it doesn't do so already, we will need to update it. On Fri, Jun 1, 2012 at 9:49 AM, Tomasz Paszkowski ss7...@gmail.com wrote: Hi, Does anyone have any idea how to implement metering of nova volumes creation/termination ? As for instances we have notifications topic. But I can't find anything similar for volumes. My first idea was to track volume creation messages but I'am afraid that attaching another consumer to volume_topic will break messages from being delivered to proper recipient. -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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 -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] [Metering] schema and counter definitions
Here is the simplified version of my code (without ampq support, counter stored directly to mysql db). https://github.com/ss7pro/rescnt Code is started from main.py which is constantly collecting counters from libvirt and storing them in a mysql database. On Mon, May 7, 2012 at 9:25 PM, Tomasz Paszkowski ss7...@gmail.com wrote: On Mon, May 7, 2012 at 5:21 PM, Loic Dachary l...@enovance.com wrote: Hi Tomasz, Hi I could not agree more and this is the reason why I/O shows in the list of meters shown in http://wiki.openstack.org/EfficientMetering (c5) disk IO in megabyte per second has a high impact on the service availability and could be billed separately . Yes but for disk drives I/O (number of read/write ops) are the key resource usage information. It's very hard to setup a billing model for disk drive usage on bandwidth as low bandwidth disk operations (small random read/writes) can utilize disk drive more than huge sequential reads/writes. I need also to mention that AWS is also charging for I/O in their volume service. It looks like you already have a codebase that could be useful for the metering implementation. Would you be willing to share it ? Yes. Just give me few days. -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] [Metering] schema and counter definitions
On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: Nice! For production code I think we are going to want to separate collection from storage, aren't we? We don't want each compute node to require access to the database server (that's an issue with nova that they are trying to fix during the folsom release, IIRC). Yes. Part of the code responsible for amqp support is not functional yet :( -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] [Metering] schema and counter definitions
I agree. Do you have any plans how to coordinate our efforts ? On Wed, May 9, 2012 at 11:11 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: On Wed, May 9, 2012 at 3:07 PM, Tomasz Paszkowski ss7...@gmail.com wrote: On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: Nice! For production code I think we are going to want to separate collection from storage, aren't we? We don't want each compute node to require access to the database server (that's an issue with nova that they are trying to fix during the folsom release, IIRC). Yes. Part of the code responsible for amqp support is not functional yet :( OK, that's what I thought. We all seem to be reinventing different parts of the services that we will eventually need, which is good for education but may be wasting a bit of energy. Is it premature to start talking a little more about architecture so we can start splitting up the implementation work and focusing that energy differently? There is a lot of work we can do independently of the remaining decisions outlined in http://wiki.openstack.org/Meetings/MeteringAgenda. -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] [Metering] schema and counter definitions
On Mon, May 7, 2012 at 5:21 PM, Loic Dachary l...@enovance.com wrote: Hi Tomasz, Hi I could not agree more and this is the reason why I/O shows in the list of meters shown in http://wiki.openstack.org/EfficientMetering (c5) disk IO in megabyte per second has a high impact on the service availability and could be billed separately . Yes but for disk drives I/O (number of read/write ops) are the key resource usage information. It's very hard to setup a billing model for disk drive usage on bandwidth as low bandwidth disk operations (small random read/writes) can utilize disk drive more than huge sequential reads/writes. I need also to mention that AWS is also charging for I/O in their volume service. It looks like you already have a codebase that could be useful for the metering implementation. Would you be willing to share it ? Yes. Just give me few days. -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova volume storage
Yes. I works perfectly (with xfs as storage backend). On Sun, May 6, 2012 at 9:30 AM, Igor Laskovy igor.lask...@gmail.com wrote: Privet Tomasz, Do you use rbd in production? Any restrictions? On Sat, May 5, 2012 at 9:50 PM, Tomasz Paszkowski ss7...@gmail.com wrote: ceph (known as rbd) :-) On Sat, May 5, 2012 at 6:06 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone! I was wondering which kind of backend storage are you using for your nova-volume? I found a lot of solutions like: LVM local Sheepdog Nexenta for NFS or NFS itself SAN GlusterFS NetApp Any ideas? Feedback? I like the GlusterFS ability to use both NFS and GlusterFS as mount point for client. They also have this 'OSConnect' functionality which provides connectivity to nova-volume and apparently performs live migration without downtime. Thank you! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Igor Laskovy -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] [Metering] schema and counter definitions
Hi,
I'd like to share my thoughts on metering openstack resources usage.
Except those data available from SystemUsageData and those mentioned
in blueprints some of the cloud providers charge for I/O on disk
drives (to prevent users from dd if=/dev/zero nosense and to teach
them properly implementing cache strategies). Those data along with
network card usage can be gathered from libvirt using domblkstat and
domifstat. My idea is to gather data using agent (or modified
nova-compute) and send them to messaging queue using following jsoned
data schema:
{'instance': 'instance-003b',
'host':'tytan-1','zone':'r4cz1','counters': {'interface': {'vnet0':
(80796L, 1212L, 0L, 0L, 53403L, 621L, 0L, 0L)}, 'disk': {'vda': (629L,
11699200L, 58L, 219136L, 0L)}}}
interface is a result of: interfaceStats(), disk is a result of: blockStats()
Those messages are consumed from queue and stored in mysql tables. I
assume that instance is a parent resource for each disk (ephemeral or
volume) and for each network interface.
So for message mentioned earlier we have three resources:
1) instances resource: instance-003b
2) child resource: vnet0 (network)
3) child resource: vda 'ephemeral
Mysql table for resources is like below:
CREATE TABLE resources (
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
parent BIGINT UNSIGNED,
type VARCHAR(255) NOT NULL,
value VARCHAR(255) NOT NULL,
zone VARCHAR(255) NOT NULL,
added TIMESTAMP,
) ENGINE=INNODB;
Counters are stored also in Mysql using following table:
CREATE TABLE counters (
resource BIGINT UNSIGNED NOT NULL,
type VARCHAR(255) NOT NULL,
value BIGINT UNSIGNED,
delta BIGINT UNISGNED,
added TIMESTAMP NOT NULL,
prev TIMESTAMP NOT NULL,
) ENGINE=INNODB;
Where prev is a reference to previous counter value. Process which is
reading data from queue is puting raw counter value into the table and
if possible (reference to previous entry present) evaluates delta
value.
By using this model of stroing usage counter's it very easy for
billing system to evaluate charges. We just run SUM(delta) on each
counter for given time range.
This model could be very easy adopted to other counters (IP Traffic
external/internal counters from iptables).
On Mon, Apr 30, 2012 at 12:15 PM, Loic Dachary l...@enovance.com wrote:
Hi,
To prepare for the next meeting ( thursday 3rd, may 2012
http://wiki.openstack.org/Meetings/MeteringAgenda ) I cleaned up and
reorganized the Metering blueprint so that it ( hopefully ) incorporates all
the information temporarily stored in the etherpad (
http://etherpad.openstack.org/EfficientMetering revision 67 in case it is
vandalized ).
We could start a discussion from the content of the following sections:
http://wiki.openstack.org/EfficientMetering#Counters
http://wiki.openstack.org/EfficientMetering#Storage
and come up with a list of the counters that should exist by default and how
they should be stored.
This morning we had a discussion with Zhongyue Luo on
irc.freenode.net#openstack-metering about how Dough could use the metering
service. Since it already knows about instance creations, counter c1 that
records how long a given instance was up is of no interest. However, other
counters such as the external bandwidth used would be useful. I advocated
that one of the advantages for Dough to rely on metering to collect counters
is that it does not need to know about each OpenStack component and can rely
on metering to figure out how to extract such counters from nova-compute,
nova-network soon to be quantum, nova-volume soon to be cinder, swift, glance
and free it from the burden of tracking structural changes.
Cheers
--
Loïc Dachary Chief Research Officer
// eNovance labs http://labs.enovance.com
// ✉ l...@enovance.com ☎ +33 1 49 70 99 82
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
Tomasz Paszkowski
SS7, Asterisk, SAN, Datacenter, Cloud Computing
+48500166299
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova volume storage
ceph (known as rbd) :-) On Sat, May 5, 2012 at 6:06 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone! I was wondering which kind of backend storage are you using for your nova-volume? I found a lot of solutions like: LVM local Sheepdog Nexenta for NFS or NFS itself SAN GlusterFS NetApp Any ideas? Feedback? I like the GlusterFS ability to use both NFS and GlusterFS as mount point for client. They also have this 'OSConnect' functionality which provides connectivity to nova-volume and apparently performs live migration without downtime. Thank you! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] Resource utilization
Please also note that diagnostics commands are not working with libvirt/qemu,kvm On Fri, Apr 20, 2012 at 1:23 PM, Razique Mahroua razique.mahr...@gmail.comwrote: Hey, I think you would look into the diagnostic calls the operator client (python-novaclient) has implemented it via $nova diagnostics, which likely give you the stats you are looking for *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 20 avr. 2012 à 13:17, Szymon Grzybowski a écrit : Is there any way to get information about resource utilization from Openstack? Any hidden API or something like that? I'm looking for statistics about CPU, RAM usage etc. both from server itself (host) and Instances (Virtual Machines) inside openstack, because i'd like to write some piece of software which could analyze those data and for example, migrate one VM to another Host. Is it possible to do this right now in Openstack? Because all i can see on dashboard are stats about instance's type. I've seen in docs something about live-migration, but i can't find openstack's way to get informations about resources. Where should i look for it in code if there is no official api, because Openstack has to collect such data right? -- *Semy* ___ 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 -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] (no subject)
On Tue, Apr 17, 2012 at 5:07 AM, cloud...@hush.com wrote: Hi, Apparently OpenStack essex release supports Rados Block Devices (RBD) in nova-volume, however I was wondering what is the usability status of these drivers? They are fully usable with Qemu/KVM as volumes and within glance as backend storage. Are the drivers complete, or even working? (I'm not saying they're not, I'm just asking before venturing deep in trying). They're fully operational as hole essex release :-) While I've seen in the nova code some references/drivers to RBD, I couldn't find any documentation on how to use it concretely. Is there any howto or anywhere that I missed? you missed them. Is RBD supported at every levels in OpenStack? - glance store image directly to RBD? backend storage (examples in default config file) - nova-volume creating RBD volumes? (apparently supported) just add lines below to nova.conf # volume volume_driver=nova.volume.driver.RBDDriver rbd_pool=nova - nova-compute spawning RBD-backed VM instances using libvirt+KVM? Working (boot from volume). One thing which is missing is image preparation. it needs to be addressed manualy (https://github.com/ceph/ceph-openstack-tools), or dirty coded within libvirt/connection.py :-) -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance can't reach dhcp or metadata
Can you show us more configuration from openvswitch (ovs-vsctl list bridge br100) ? ovs-vsctl list bridge br100 On Tue, Apr 10, 2012 at 12:44 PM, Nicolas de BONFILS ndebonf...@gmail.com wrote: Hi, I try it, and it doesn't change anything :( Quantum still assign an ip to the VM, but the VM still doesn't ping the dhcp server when it boot. I believe it's a bridge/interface problem. --- Nicolas On Mon, Apr 9, 2012 at 18:41, Dan Wendlandt d...@nicira.com wrote: On Mon, Apr 9, 2012 at 4:57 AM, Nicolas de BONFILS ndebonf...@gmail.com wrote: Hi, Thanks for the advice but I instead of using FlatManager, I use QuantumManager (network_manager=nova.network.quantum.manager.QuantumManager) Also, to be more accurate, Quantum assign an ip to my VM (I see it in horizon and in nova/quantum mysql db), but the VM doe not get it. Hi Nicolas, You may be hitting a known issue with QuantumManager + DHCP + Melange: - https://bugs.launchpad.net/quantum/+bug/949234 Looks like a partial fix was suggested for QuantumManager in Nova, but validation ran into a possible melange issue, that ultimately was rejected, without submitting the QuantumManager fix: - https://bugs.launchpad.net/melange/+bug/951499 Can you try just applying the one-liner patch described in 949234 and see if it solves your problem? If so, we can get that merged in. Dan Regards --- Nicolas On Mon, Apr 9, 2012 at 13:04, raja.me...@wipro.com wrote: Hi Nicolas, You need another interface ( say eth1 UP running ) . Configure br100 to use eth1 . typically your configuration will look like the below .. /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto eth1 auto br100 iface br100 inet static bridge_ports eth1 address 10.0.0.1 netmask 255.255.255.0 bridge_stp off bridge_fd 0 nova.conf will have the following lines too.. --fixed_range=10.0.0.0/24 --network_size=256 --network_manager=nova.network.manager.FlatManager --flat_interface=eth1 --flat_injected=False --public_interface=eth0 Meena Raja Consultant __ WIPRO TECHNOLOGIES No 53/1 Ganapa Towers ,Near Madivala Police Station , Hosur Main Road ,Bangalore-560068 Hand Phone : +91-9880549725 | Desk : +91-80-39912554 |Fax No: +91-80-25502160 Email : raja.me...@wipro.com | Website : www.wipro.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Instance can't reach dhcp or metadata
nova.compute.manager [-] FLAGS.reclaim_instance_interval = 0, skipping... from (pid=28534) _reclaim_queued_deletes /openstack/nova/nova/compute/manager.py:2380 2012-04-10 15:37:56 DEBUG nova.manager [-] Running periodic task ComputeManager._report_driver_status from (pid=28534) periodic_tasks /openstack/nova/nova/manager.py:152 2012-04-10 15:37:56 INFO nova.compute.manager [-] Updating host status 2012-04-10 15:37:56 DEBUG nova.virt.libvirt.connection [-] Updating host stats from (pid=28534) update_status /openstack/nova/nova/virt/libvirt/connection.py:2591 2012-04-10 15:38:00 DEBUG nova.manager [-] Running periodic task ComputeManager._poll_unconfirmed_resizes from (pid=28534) periodic_tasks /openstack/nova/nova/manager.py:152 2012-04-10 15:38:00 DEBUG nova.utils [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] Running cmd (subprocess): sudo /usr/local/bin/nova-rootwrap ovs-vsctl -- --may-exist add-port br-int tap661cb0d2-03 -- set Interface tap661cb0d2-03 external-ids:iface-id=661cb0d2-03f6-4129--30f5be65cada -- set Interface tap661cb0d2-03 external-ids:iface-status=active -- set Interface tap661cb0d2-03 external-ids:attached-mac=FE:EE:DD:00:00:0E -- set Interface tap661cb0d2-03 external-ids:vm-uuid=d0c21b65-2957-40cc-a3db-887cf7c959ee from (pid=28534) execute /openstack/nova/nova/utils.py:220 2012-04-10 15:38:01 DEBUG nova.virt.libvirt.config [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] Generated XML domain type=qemu uuidd0c21b65-2957-40cc-a3db-887cf7c959ee/uuid nameinstance-000f/name memory524288/memory vcpu1/vcpu os typehvm/type kernel/openstack/nova/instances/instance-000f/kernel/kernel initrd/openstack/nova/instances/instance-000f/ramdisk/initrd cmdlineroot=/dev/vda console=ttyS0/cmdline /os features acpi/ /features devices disk type=file device=disk driver type=qcow2 cache=none/ source file=/openstack/nova/instances/instance-000f/disk/ target bus=virtio dev=vda/ /disk interface type=ethernet mac address=FE:EE:DD:00:00:0E/ script path=/ target dev=tap661cb0d2-03/ /interface serial type=file source path=/openstack/nova/instances/instance-000f/console.log/ /serial serial type=pty/ input type=tablet bus=usb/ graphics type=vnc autoport=yes keymap=en-us listen=127.0.0.1/ /devices /domain from (pid=28534) to_xml /openstack/nova/nova/virt/libvirt/config.py:62 2012-04-10 15:38:01 DEBUG nova.virt.libvirt.connection [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] [instance: d0c21b65-2957-40cc-a3db-887cf7c959ee] Finished toXML method from (pid=28534) to_xml /openstack/nova/nova/virt/libvirt/connection.py:1644 2012-04-10 15:38:01 INFO nova.virt.libvirt.firewall [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] [instance: d0c21b65-2957-40cc-a3db-887cf7c959ee] Called setup_basic_filtering in nwfilter 2012-04-10 15:38:01 INFO nova.virt.libvirt.firewall [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] [instance: d0c21b65-2957-40cc-a3db-887cf7c959ee] Ensuring static filters 2012-04-10 15:38:01 DEBUG nova.virt.firewall [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] Adding security group rule: nova.db.sqlalchemy.models.SecurityGroupIngressRule object at 0x47a0cd0 from (pid=28534) instance_rules /openstack/nova/nova/virt/firewall.py:291 2012-04-10 15:38:01 INFO nova.virt.firewall [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] Using cidr u'10.0.0.0/24' 2012-04-10 15:38:01 INFO nova.virt.firewall [req-bc5aac98-6c23-4bbe-8ec3-d8bc671ea4f1 94157c6bf9ad4753ab8e1f8c20617cbb 1e00e717a3a3487381dfe5f8e7f63c92] Using fw_rules: ['-m state --state INVALID -j DROP', '-m state --state ESTABLISHED,RELATED -j ACCEPT', '-j $provider', '-s None -p udp --sport 67 --dport 68 -j ACCEPT', u'-s 10.0.0.0/24 -j ACCEPT', u'-j ACCEPT -p tcp --dport 22 -s 10.0.0.0/24'] --- Nicolas -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] Keystone get user-by-name
Hi, I'am trying to write code responsible for password reset in keystone. Is there an API call which allows to get user_id by name without fetch all defined users ? -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ 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] running glance index got Details [errno 111] ECONNREFUSED erro
Put appropriate glance configuration into nova.conf on nova-compute node, like below: glance_port=9292 glance_api_servers=10.0.0.1:9292 glance_num_retries=0 glance_host=10.0.0.1 On Wed, Mar 28, 2012 at 9:54 AM, 下一个傻子 nextf...@gmail.com wrote: I followed all the steps ,until step 4 ,when I run glance index ,I got the following, CientConnectionError：there was an error connecting to an server Details [errno 111] ECONNREFUSED what's really confusing me is I did all the steps yesterday and everything is just fine until ssh to the VM,but today ,I did all the steps again and got stuck on step 4 ,and got the above error. Someone please help me :) Thank you! On Wed, Mar 28, 2012 at 3:14 AM, Guilherme Souza souza.guilherm...@gmail.com wrote: my templates directory was bad configured, then the keystone was stopped, i just fix the directory and restart keystone. Em 27 de março de 2012 15:58, Martin Gerhard Loschwitz martin.loschw...@hastexo.com escreveu: Am 27.03.12 20:53, schrieb Guilherme Souza: I got this, just ignore my messages! =D What was wrong? Maybe others stumble across the same problems and would be happy to find the solution :) Or maybe we should make a note in the document if something in there needs clarification ... Best regards Martin -- Martin Gerhard Loschwitz Chief Brand Officer, Principal Consultant hastexo Professional Services CONFIDENTIALITY NOTICE: This e-mail and/or the accompanying documents are privileged and confidential under applicable law. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof. Should you have received this e-mail (or any copy thereof) in error, please let us know by telephone or e-mail without delay and delete the message from your system. Thank you. -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Stay with me,stay with my heart,honey. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Tomasz Paszkowski SS7, Asterisk, SAN, Datacenter, Cloud Computing +48500166299 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
