i installed keystone on centos- 192.168.5.29 and i stopped iptables in
centos then i installed swift on ubuntu- 192.168.5.37 where ufw
stop/waiting (swift working well all
servers-proxy,account,containeer,object- are working but when i run this
command on ubuntu swift
swift -V 2.0 -A
Hi ,
First of all check whether VM is getting the desired IP or not jst by
logging into it if you have KVM use Virt-manager .
do ifconfig
if IP is there then try to set your switch in *promisc mode .*
Hopefully this solves your problem.
On Fri, Mar 29, 2013 at 1:52 PM, zengshan2008
Hi Beshoy ,
Could you please provide the following information ?
1) First issue is that the Keystone running on 192.168.5.29 , And the
AUTH_URL in swift-client should point to authentication server(keystone in
your case) . The command should be :
swift -V 2.0 -A http://192.168.5.29:5000/v2.0
Hi,
Have you added rules in the security group.
For ping to work ICMP rule needs to be added and for SSH to work TCP rule
needs to be added.
Check the following doc for more details
http://docs.openstack.org/folsom/openstack-compute/admin/content/instance-networking.html
Regards,
Sagar
On
Really, a good job!
Tks, Marco.
2013/3/29 skible openstack skible.openst...@gmail.com
Hi Stackers,
I present to you my new guide : OpenStack Grizzly Install Guide by Bilel
Msekni. https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide
This is an easy way to deploy Grizzly on a
Vish:
I suspect there's a Grizzly doc bug here.
The Folsom docs say
http://docs.openstack.org/folsom/openstack-compute/admin/content/specify-host-to-boot-instances-on.html
:
With the Folsom release it is no longer possible to indicate a specific
compute host to use to boot an instance with the
Woops, hit send too soon.
I made the doc change based on this mailing list post by Phil Day.
https://lists.launchpad.net/openstack/msg19784.html
Which was in this doc bug:
https://bugs.launchpad.net/openstack-manuals/+bug/1096168
Phil, can you verify on a grizzly install and post the correct
I made the doc edit based on this mailing list post from Phil Day.
https://lists.launchpad.net/openstack/msg19784.html
On Sun, Mar 31, 2013 at 9:03 PM, Lorin Hochstein
lo...@nimbisservices.comwrote:
Vish:
I suspect there's a Grizzly doc bug here.
The Folsom docs say
Anne:
I read that as meaning you can now control who has access to do this via
policy.json, but the UI for doing it still uses the --availability-zone
flag. I documented my understanding here:
https://review.openstack.org/25804, but we should wait for Phil Day's
response.
Lorin
On Sun, Mar
Hi,
While using a OVS plugin based Quantum setup, will it be possible to go
beyond 4095 vlans by re-using them across multiple physnets. For example,
is something like the setting below possible?
network_vlan_ranges = physnet1:1:4094, physnet2:1:4094,
Or will this not be allowed due to
Hi:
I am integrating floodlight with openstack quantum, but the bigswitch
restproxy plugin seems have some error in the latest git version:
the quantum-server and l3-agent log give the following errors:
File
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/8/Project:precise_havana_cinder_trunkDate of build:Sun, 31 Mar 2013 02:31:33 -0400Build duration:1 min 5 secBuild cause:Started by an SCM changeBuilt
Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/9/Project:precise_havana_cinder_trunkDate of build:Sun, 31 Mar 2013 11:31:32 -0400Build duration:1 min 4 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_stable/718/Project:precise_folsom_nova_stableDate of build:Sun, 31 Mar 2013 15:01:36 -0400Build duration:1 min 58 secBuild cause:Started by an SCM changeBuilt
14 matches
Mail list logo
