--bypass-url bypass-url
Use this API endpoint instead of the Service
Catalog
In client.py :
if self.bypass_url:
self.set_management_url(self.bypass_url)
Is this what you expect ?
-Sylvain
Le 13/02/2013 12:08, Patrick Petit a écrit :
Dear All,
I forgot to mention, cinderclient doesn't support this attribute yet,
but it's worth to add it.
-Sylvain
Le 13/02/2013 12:46, Sylvain Bauza a écrit :
--bypass-url bypass-url
Use this API endpoint instead of the Service
Catalog
In client.py
First of all, make sure metadata is
DNAT'd to nova-api on your nova-network node.
For that, please issue 'iptables -t nat -S' and look at the
corresponding entry :
-A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp
--dport 80 -j DNAT
First of all, make sure metadata is DNAT'd to nova-api on your
nova-network node.
For that, please issue 'iptables -t nat -S' and look at the
corresponding entry :
-A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport
80 -j DNAT --to-destination ip:8775
If this is correct,
Le 15/02/2013 11:42, Chathura M. Sarathchandra Magurawalage a écrit :
How can I log into the VM from VNC? What are the credentials?
You have multiple ways to get VNC access. The easiest one is thru
Horizon. Other can be looking at the KVM command-line for the desired
instance (on the
have to create ssh key
pair and download the ssh key. You can create this ssh pair using
horizon/cli.
On Fri, Feb 15, 2013 at 4:27 PM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com
wrote:
Le 15/02/2013 11:42, Chathura M. Sarathchandra
Hi,
Nova is generating libvirt.xml for each instance with cpu
mode=host-model match=exact/
As a result, virsh (and nova-compute) refuses to start instance as
complaining :
error : internal error Cannot find suitable CPU model for given data
Libvirt is 0.9.13-0ubuntu12.2~cloud0 and kvm is
Le 15/02/2013 18:20, Lukáš Vízner a écrit :
Hi,
I have problem with this issue. I have installed OpenStack Folsom
succesfully by
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
I do not know why, but after few days when
, Sylvain Bauza sylvain.ba...@digimind.com wrote:
Hi,
Nova is generating libvirt.xml for each instance with cpu mode=host-model
match=exact/
As a result, virsh (and nova-compute) refuses to start instance as complaining :
error : internal error Cannot find suitable CPU model for given data
Hi,
I'll try to be clear. I do follow a classic setup for Quantum with 2
NICs and a GRE tunnel in between nodes with br-int/br-tun.
Everything is fine at first install, but when rebooting the network node
(including quantum-ovs-plugin-agent, quantum-l3-agent and
quantum-dhcp-agent), I
Hi Greg,
I did have trouble with DHCP assignation (see my previous post in this
list), which was being fixed by deleting ovs bridges on network node,
recreating them and restarting OVS plugin and L3/DHCP agents (which were
all on the same physical node).
Maybe it helps.
Anyway, when
.
Other terms, GRE tunneling is fine at reboot, only interface status is
wrong.
Do you have any idea how to fix it ? I can't issue a 'post-up' statement
in /etc/network/interfaces and /etc/rc.local is quite a ugly patch I think.
Thanks,
-Sylvain
Le 18/02/2013 18:06, Sylvain Bauza a écrit :
Hi
Le 19/02/2013 13:31, Gary Kotton a écrit :
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following Provided Router/single tenancy setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: BROADCAST
Hi,
I have a classic Provider Network, private networks as follows :
- internal network 10.0.0.0/24
- external network 192.168.10.0/24 gw 192.168.1.252 (I know, I have to
add a manual route on both gw and network node)
- br-ex is having 192.168.10.254
I have a floating IP 192.168.10.2
192.168.10.00.0.0.0 255.255.255.0 U 0 00 br-ex
(I also removed the default entry for eth0 (mngmt interface), as it was
nonsense).
-Sylvain
Le 19/02/2013 20:39, Sylvain Bauza a écrit :
Hi,
I have a classic Provider Network, private networks as follows :
- internal
do the trick either.
Any idea ?
Thanks,
-Sylvain
Thanks,
-Sylvain
Le 18/02/2013 18:06, Sylvain Bauza a écrit :
Hi,
I'll try to be clear. I do follow a classic setup for Quantum with 2
NICs and a GRE tunnel in between nodes with br-int/br-tun.
Everything is fine at first install
='0.0.0.0'/
/graphics
Try in nova-compute.conf :
vncserver_proxyclient_address=compute node mgmt IP
vncserver_listen=compute node mgmt IP
and in nova.conf :
novncproxy_base_url=http://controler node mgmt IP:6080/vnc_auto.html
and restart nova-compute.
On 20 February 2013 11:57, Sylvain Bauza
Hi,
Previously using nova-network, all my VMs were having :
# route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use Iface
10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0
169.254.0.0 0.0.0.0 255.255.0.0
Le 20/02/2013 23:04, Chathura M. Sarathchandra Magurawalage a écrit :
Thanks.
I would be more concerned about the SIOCDELRT error above. Do you
try to manually remove a network route at bootup ? Seems like the
'route del' is failing because the route is not already existing.
I am
, Sylvain Bauza a écrit :
Hi,
Previously using nova-network, all my VMs were having :
# route -n
Table de routage IP du noyau
Destination Passerelle Genmask Indic Metric Ref Use
Iface
10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0
169.254.0.0 0.0.0.0
Have you checked your Glance credentials using 'glance index' ?
On Thu, Feb 21, 2013 at 5:09 PM, Muhammad Kazim kazima...@gmail.com
mailto:kazima...@gmail.com wrote:
Hi,
I am installing OpenStack, i have installed all services including
Nova, Keystone, Glance. I run this command
I did had trouble with DHCP leasing with 2K3 R2 using Essex. At first
boot, the lease was taken from our corporate DHCP server instead of
nova-network dnsmasq.
I also noticed in EventViewer that, as you mention, DHCP leases were
sometimes forgotten.
After long time investigating, I had to
Hi Shawn,
Le 25/02/2013 06:20, Shawn Starr a écrit :
Hello folks,
I am starting to look at OpenStack and noticed there are some things it
doesn't seem to be able to do right now?
1) Managing the nova-compute (hypervisor) - I see no options on how to control
what nova-compute nodes can be
Yet no reply ?
I did the hack, I removed the 169.254.0.0/16 route from my images, but
this is quite a ugly hack.
Could someone with OpenVswitch/GRE setup please confirm that there is no
route to create for metadata ?
Thanks,
-Sylvain
Le 21/02/2013 11:33, Sylvain Bauza a écrit :
Anyone ?
I
at 8:36 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Yet no reply ?
I did the hack, I removed the 169.254.0.0/16
http://169.254.0.0/16 route from my images, but this is quite a
ugly hack.
Could someone with OpenVswitch/GRE setup please
Could you please paste your keystone.conf ?
Also, could you please check keystone service is started ?
-Sylvain
Le 27/02/2013 15:06, Tomás( S(oltys a écrit :
Hi,
I am trying to setup keystone myself on CentOS using this step-by-step
instructions:
Metadata can be fetched from http://169.254.169.254:80/latest/metadata
Could you please tcpdump -nn -i your bridge intf. on your node running
nova-network and check if you see request coming in ?
-Sylvain
Le 28/02/2013 17:29, mohammad kashif a écrit :
Hi
I have installed openstack on two
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Try to delete/recreate your br-int/br-ex and then restart
openvswitch_plugin/l3/dhcp agents, it should fix the issue.
-Sylvain
Le 01/03/2013 15:04, The King in Yellow a écrit :
In
, 2013, at 9:11 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com
wrote:
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Hmm. Reading that page, it's not clear to me exactly where
at 10:11 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Try to delete/recreate your br-int/br-ex and then restart
Le 04/03/2013 19:45, Dan Wendlandt a écrit :
On Mon, Mar 4, 2013 at 6:44 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Another classic error is to forget to add a static route from the
controller node (if hosting metadata service
If you look at
http://www.pixelbeat.org/docs/openstack_libvirt_images/#1361764412,
you'll see that resize2fs is performed. But there is a caveat with RHEL6
which is Linux 2.6 (contrary to Ubuntu 12.04 which is Linux 3.0).
If you look at man resize2fs :
The resize2fs program will resize
Could you please tell us what is your libvirt_cpu_model ?
Please check both nova.conf and instance's libvirt.xml.
-Sylvain
Le 05/03/2013 11:30, Balamurugan V G a écrit :
Hi,
I am running Folsom 2.2 with a KVM compute node. When I launch a
windows instance with flavor that has 2 VCPUs and 2Gb
it on something like rc.local? Or is quantum plugins'
responsibility to run the utility?
2013/3/1 Sylvain Bauza sylvain.ba...@digimind.com
mailto:sylvain.ba...@digimind.com
There is a known bug for the network bridges, when rebooting :
https://bugs.launchpad.net/quantum/+bug/1091605
Try
/03/2013 15:26, The King in Yellow a écrit :
On Mon, Mar 4, 2013 at 3:18 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Is the network node also acting as a Compute node ?
No, I am running three separate nodes-- network, compute and controller
Le 05/03/2013 13:57, Filipe Manco a écrit :
Ok
I'm using the script (I'm calling it from rc.local) and everything
works fine, even for instances that already exist.
Thanks
The bug is related to the tap device, ie. DHCP agent reboot.
The second bug I mentioned is related to a compute node
vnet3
root@os-compute-01:~#
On Tue, Mar 5, 2013 at 8:02 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
You get it. This is the bug I mentioned related to compute nodes.
Folks, anyone knowing the bug tracking numbre, btw ?
'ovs-dpctl show
I forgot to mention, could you please also check that
quantum-openvswitch-agent is started ('ps -ef' ) ?
Le 05/03/2013 17:19, Sylvain Bauza a écrit :
You should be close to the solution. Looking at your GRE tunnels, I
only see a one-to-one tunnel in between your compute node and your
network
Le 05/03/2013 18:14, The King in Yellow a écrit :
I'm not clear on what the interfaces are, but q-9f9041ce-65 is
10.5.5.1 on the network node, so he seems to be seeing the traffic.
tap45ffdc5f-da is listed as 10.5.5.2, and I have no idea what function
that is performing.
qr-X is the
-int and restart all quantum-*-agents on the network node.
Sorry, can't help further :-(
-Sylvain
Le 06/03/2013 18:45, The King in Yellow a écrit :
On Wed, Mar 6, 2013 at 10:15 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Le 05/03/2013 18:14
Could you please tell us :
- your credentials (except password of course)
- 'keystone endpoint-list'
- 'keystone service-list'
It seems like you're requesting a wrong API.
Is 'nova list' working btw ?
-Sylvain
Le 08/03/2013 12:56, Ashutosh Narayan a écrit :
Services nova-compute,
|
| d307d545040e4bda8ace9a7fd3581cb2 | keystone | identity |
Keystone Identity Service |
+--+--+--+---+
nova list also throws the same error.
On Fri, Mar 8, 2013 at 5:44 PM, Sylvain Bauza
sylvain.ba...@digimind.com
)' - hence the creation of Path MTU discovery in the
first place. :)
FWIW, in the IPv6 world, routers do not fragment. That implies either
functioning PathMTU discovery, or lowest common MTU...
Aaron
On Fri, Mar 8, 2013 at 9:08 AM, Sylvain Bauza
sylvain.ba...@digimind.com wrote:
Hi,
I recently
I also forgot to mention: I'm using a typical Openvswitch setup with GRE
encapsulation.
I can't proof, but would GRE not able to work with PathMTU ?
-Sylvain
Le 11/03/2013 09:40, Sylvain Bauza a écrit :
Hi Rick, reply inline.
Le 08/03/2013 20:27, Rick Jones a écrit :
On 03/08/2013 09:55 AM
would be great).
Le 11/03/2013 10:07, Sylvain Bauza a écrit :
I also forgot to mention: I'm using a typical Openvswitch setup with
GRE encapsulation.
I can't proof, but would GRE not able to work with PathMTU ?
-Sylvain
Le 11/03/2013 09:40, Sylvain Bauza a écrit :
Hi Rick, reply inline
So as to reproduce the nova-manage SQL command, I would recommand to
tcpdump -A port 3306 on the host and get the SQL trace on what's failing.
Could you please explain further what is your HA config ? Are you using
pacemaker/heartbeat or any VIP ?
-Sylvain
Le 11/03/2013 14:23, Samuel
Le 12/03/2013 09:20, Robert van Leeuwen a écrit :
Only changing the VM MTU to 1454 does the trick ('ifconfig eth0 mtu 1454').
I think this is the same issue:
https://bugs.launchpad.net/quantum/+bug/1075336
So instead of decreasing the MTU on the physical interface you could also
increase it
Le 12/03/2013 13:12, Robert van Leeuwen a écrit :
I thought about it, but yet not tried. Which OVS port would you
recommend to increase MTU ?
On the network node (br-ex or qg-) , or on the compute node (br-int) ?
You need to set it on the compute nodes ( int-br-ethX ) and possibly the an
Le 15/03/2013 08:20, Sammy Fung a écrit :
I am following this nice guide to configure Quantum.
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst
SNIP
I got timeout on HTTP request to 169.254.169.254 connecting from
Hi,
I don't understand your business. Should you have a 192.168.1.0/24
network for management, you could also assign an external network with
Quantum based on the same subnet (ie. 192.168.1.0/24).
When creating a floating IP pool, Quantum does require at least 3 things :
- the CIDR
- the
this?
Thanks.
On 18 March 2013 15:50, Sylvain Bauza sylvain.ba...@digimind.com
mailto:sylvain.ba...@digimind.com wrote:
Hi,
I don't understand your business. Should you have a 192.168.1.0/24
http://192.168.1.0/24 network for management, you could also
assign an external network
be done on virtual box using a bridge
adapter which maps the VM in to the physical network.
On 18 March 2013 16:05, Sylvain Bauza sylvain.ba...@digimind.com
mailto:sylvain.ba...@digimind.com wrote:
Could you please tell me your physical network CIDR ?
Anyway, what you need is not requiring
:44, Chathura M. Sarathchandra Magurawalage a écrit :
Thanks.
its 192.168.2.0/24 http://192.168.2.0/24
free ip range: 192.168.2.151 192.168.2.240
gw/dhcp server: 192.168.2.253
On 19 March 2013 08:28, Sylvain Bauza sylvain.ba...@digimind.com
mailto:sylvain.ba...@digimind.com wrote
Le 20/03/2013 13:24, Mohammed Amine SAYA a écrit :
RuntimeError:
Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf',
'ovs-vsctl', '--', '--may-exist', 'add-port', 'br-ex', 'qg-32dd6c6b-b6', '--',
'set', 'Interface', 'qg-32dd6c6b-b6', 'type=internal', '--', 'set',
'Interface',
channel_id: 1
2013-03-20 14:23:17DEBUG [amqplib] Channel open
Thanks for your help,
Amine.
On Wed, Mar 20, 2013 at 2:15 PM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Le 20/03/2013 13:24, Mohammed Amine SAYA a écrit :
RuntimeError
Hi,
As per https://bugs.launchpad.net/quantum/+bug/1155050 and also other
litterature, I do see doc alerts saying that Quantum L3 and DHCP agents
must be on different hosts.
Let me be honest, I successfully installed and configured both on the
same physical machine, using GRE tunnels and
Hi Gary,
Le 20/03/2013 17:26, Gary Kotton a écrit :
Yes, this works. The problem is ensuring the network isolation. That
is, someone can make changes in the routing table on the host which
will enable one to gain access to the quantum networks. That is why we
suggest that they run on different
Hi Johanna,
Le 22/03/2013 14:36, Heinonen, Johanna (NSN - FI/Espoo) a écrit :
Hi,
We want somehow to add a new interface to a running VM. To modify an
existing interface (by assigning it to a new subnet) could be also an
alternative.
Quantum port-update port-id --fixed_ip
the controller or any other
physical nodes.
Any idea?
On 19 March 2013 16:14, Sylvain Bauza sylvain.ba...@digimind.com
mailto:sylvain.ba...@digimind.com wrote:
As per
http://docs.openstack.org/folsom/openstack-network/admin/content/demo_logical_network_config.html
but slightly
Le 25/03/2013 12:49, Chathura M. Sarathchandra Magurawalage a écrit :
I have got one question on this. Does quantum directly request leases
from the gateway of the physical network before reserving them to
allocate to VMs?
Nope, not at all. It's up to the administrator to make sure the
Le 25/03/2013 16:00, Chathura M. Sarathchandra Magurawalage a écrit :
I can not see anything going through qg- interface.
Your iptables seem correct.
Could you please ip a and make sure floating ip is bound to qg- ?
Are you sure that floating IPs are working properly on your setup ?
Hi,
I created two host aggregates, one per host with extra_specs and flavors
associated as given in [1]. Unfortunately, while the first created
instance with the desired flavor is launching on the right host, the
second instance with the same flavor is not spawning on the same host,
but on
Folks, forget it.
I had wrong nova.conf settings before I posted, which I modified. I also
restarted nova-scheduler, but it seems I forgot to restart once more
after the *last* change.
Now, the below values are correct.
Thanks,
-Sylvain
Le 27/03/2013 16:36, Sylvain Bauza a écrit :
Hi,
I
Agree.
As for other shared FS, this is *highly* important to make sure Nova UID
and GID are consistent in between all compute nodes.
If this is not the case, then you have to usermod all instances...
-Sylvain
Le 11/04/2013 16:49, Razique Mahroua a écrit :
Hi JP,
my bet is that this is a
Have you tried to look at the RabbitMQ web interface to see what could
be stuck ?
Activating it is quite straightforward, as per Ops Guide :
http://docs.openstack.org/trunk/openstack-ops/content/logging_monitoring.html#rabbitmq
-Sylvain
Le 12/04/2013 17:48, Lowery, Mathew a écrit :
Hi all,
Try issuing sudo virsh list --all to get all XML files defined.
-Sylvain
Le 16/04/2013 11:14, Wangpan a écrit :
Firstly, it may because your services stopped running, as you list at
the last mail.
so you can't create an instance successfully.
Otherwise, it may because you should add sudo
Hi Anil,
What you quoted is about L3 management and bridging and the need of
flexibility. It means that the physical NIC will have a whole bunch of
IP addresses, one per Quantum router you define.
Should you want to deploy a Controler on that node, you would need to
have a second NIC with
Waiting Daniel's reply, but afaik, the new NBD server is available since
qemu-1.4 and libvirt 1.0.2
Daniel, feel free to confirm or blame me.
Btw, kvm capabilities are available in upstream qemu since qemu-1.3
which works like a charm with Nova (Folsom).
-Sylvain
Le 24/04/2013 23:23, Lorin
Indeed. There is room for improvement :
should the 2 disks be RAID1 or parts of the same VG, as said ?
As it is recommended hardware, it would be interesting to know
which kind of setup with 2 SATA disks is optimal ?
Of course, it does depend a lot
Hi John,
Le 30/04/2013 18:13, John Griffith a écrit :
Hi Sylvain,
This doc is a bit outdated and references Nova Volumes etc, however
the problem I think you're having is that it makes some assumptions
regarding knowledge of how all the components tie together and what
they do. They're
I would give my vote to Island, which is pretty universal and at the
same time referring to what HK is : an island.
Le 02/05/2013 16:01, Thierry Carrez a écrit :
Hi everyone,
As you may know, we name our release cycles after cities or counties in
the state/country where the corresponding
Hi,
It sounds quite unclear for me about the possibility *in Folsom* to have
two distinct Cinder hosts having each one LVM backend called
cinder-volumes ?
As per the doc [1], I would say the answer is no, but could you please
confirm ?
If so, do you have any idea on how to trick a nearly
Le 30/05/2013 15:25, Sylvain Bauza a écrit :
Hi,
It sounds quite unclear for me about the possibility *in Folsom* to
have two distinct Cinder hosts having each one LVM backend called
cinder-volumes ?
As per the doc [1], I would say the answer is no, but could you please
confirm ?
If so
Putting openstack-ops@ in the loop :-)
Le 30/05/2013 17:26, Sylvain Bauza a écrit :
Le 30/05/2013 15:25, Sylvain Bauza a écrit :
Hi,
It sounds quite unclear for me about the possibility *in Folsom* to
have two distinct Cinder hosts having each one LVM backend called
cinder-volumes
://docs.openstack.org/folsom/openstack-compute/install/apt/content/osfolubuntu-cinder.html
Regards,
Jérôme
On Fri, May 31, 2013 at 9:21 AM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba...@digimind.com wrote:
Putting openstack-ops@ in the loop :-)
Le 30/05/2013 17:26
is not available in Folsom: you can only run
one cinder-volume per compute (in that case, if you want to manage
several backends, you have to have several computes).
Thanks a lot for your remarks,
Jérôme
On Fri, May 31, 2013 at 1:55 PM, Sylvain Bauza
sylvain.ba...@digimind.com mailto:sylvain.ba
Hi Anne,
Thanks for the quick reply.
Le 04/06/2013 16:00, Anne Gentle a écrit :
If that's all a bit too much, we can work on it from your blog entry,
I've created this doc bug to track the work:
https://bugs.launchpad.net/openstack-manuals/+bug/1187400. Feel free
to assign yourself.
Hi,
While I was working on Essex, I was simply looking at the image UUID and
copying it from /var/lib/glance/images, that's it.
I was not aware of glance image-download, which is great (same command
for all Glance backends).
-Sylvain
Le 20/06/2013 11:53, Michael Still a écrit :
I'm not
Hi Paul,
Apologies if I missed any related info, but how to subscribe to the new
lists.openstack.org list ?
I can't find my way thru mailman [1]
Thanks,
-Sylvain
[1] : http://lists.openstack.org/cgi-bin/mailman/listinfo
Le 24/07/2013 18:19, Paul Hummer a écrit :
Openstackers-
You've
IRC pcm_ (irc.freenode.net http://irc.freenode.net)
TW @pmichali
On Jul 25, 2013, at 3:06 AM, Sylvain Bauza sylvain.ba...@bull.net
mailto:sylvain.ba...@bull.net wrote:
Hi Paul,
Apologies if I missed any related info, but how to subscribe to the
new lists.openstack.org http
Le 25/07/2013 18:34, Thierry Carrez a écrit :
My understanding is that the current subscriptions will be migrated to
the new list automatically. I suspect that direct subscription will not
be available until the migration occurred.
Thanks, hope so as well.
Could s/o clarify ?
-Sylvain
81 matches
Mail list logo
