On 01/22/2013 07:02 PM, Jian Wen wrote:
On 2013?01?22? 10:56, Balamurugan V G wrote:
Hi,
In an Openstack deployment using Quantum, the compute nodes access
the public/external network via the network node (as per the diagram
Hi friends,
I have got the idea about this by komobo and devstack.
komobo is powerful that can debug remote python,perl,php...etc
if you have the same question about it, you can email to me, I will help
you.
Good Luck.
Lawrency Meng
mail:
+1
On 1/23/13 4:30 PM, longeek mengql112...@gmail.com wrote:
Hi friends,
I have got the idea about this by komobo and devstack.
komobo is powerful that can debug remote python,perl,php...etc
if you have the same question about it, you can email to me, I will help
you.
Good Luck.
These are great news Gary.
Do you happen to know if the patch will be also available for folsom?
Thanks,
Gabriel
From: Gary Kotton gkot...@redhat.com
To: jian@canonical.com
Cc: openstack@lists.launchpad.net
Sent: Wednesday, January 23, 2013 10:08 AM
Hi Razique,
I ran this command :
alex@alex-X9SCD:~$ egrep '^flags.*(vmx|svm)' /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl
Hi,
I'm trying to use multinic to create a scenario with two instances: Client
(with one network interface) and Router (with two interfaces):
Client(10.0.14.5) (10.0.14.9)Router(10.0.2.9)
I have modified the gateway in Client routing table, setting Router as the
new gateway, and activated
Hi.
I'm experimenting with some odd fundamental ideas about storage currently
for my deployment.
Earlier on this list, we were discussing a way to pin or segregate certain
instances to certain node types. There appears to be a quite neat way to do
this using a filter-scheduler configuration and
I see that there is no value being passed for 'bridge'. The snippet from
the nova-compute log just before the Execption is below:
2013-01-23 02:33:37 DEBUG nova.compute.manager
[req-9c972e4e-3f8b-4cc3-b151-963b71f0b9a2 9ac7dbe62fb349ce84927598a0f54d68
b439758af3814f739fe7ab09b98a0120] [instance:
Hi,
I'm trying to use multinic to create a scenario with two instances: Client
(with one network interface) and Router (with two interfaces):
Client(10.0.14.5) (10.0.14.9)Router(10.0.2.9)
I have modified the gateway in Client routing table, setting Router as the
new gateway, and activated
Ok,now :sudo modprobe kvmsudo modprobe kvm-intelYou should be good I think
Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15
Le 23 janv. 2013 à 10:34, Alexandre De Carvalho alexandre7.decarva...@gmail.com a écrit :Hi Razique,I ran this command :alex@alex-X9SCD:~$ egrep
Try this as well:
chown root:kvm /dev/kvm
-Balu
On Wed, Jan 23, 2013 at 4:51 PM, Razique Mahroua
razique.mahr...@gmail.comwrote:
Ok,
now :
sudo modprobe kvm
sudo modprobe kvm-intel
You should be good I think
*Razique Mahroua** - **Nuage Co*
razique.mahr...@gmail.com
Tel : +33 9 72
Hi Stackers-
I have installed glance and Keystone and configured them.
But When I upload a test image with glance, I got this error in keystone
logs
(sqlalchemy.engine.base.Engine): 2013-01-23 17:04:57,904 INFO
('106298a47e5a4d129c7b8571e188c51e', 1)
(keystone.common.cms): 2013-01-23
+1
On 01/22/2013 07:25 PM, Vishvananda Ishaya wrote:
+1
We mentioned previously that we would fast-track former core members back in.
I gess we can wait a couple of days to see if anyone objects and then add him
back.
Vish
On Jan 22, 2013, at 3:38 PM, Matt Dietz matt.di...@rackspace.com
+1
On Jan 22, 2013, at 5:38 PM, Matt Dietz matt.di...@rackspace.com wrote:
All,
I think Trey Morris has been doing really well on reviews again, so I'd
like to propose him to be reinstated for Nova core. Thoughts?
-Dietz
___
Mailing
Hi,
I wonder how the Windows Licensing would work in OpenStack. Lets say I have
a Windows Image which I have already activated. Now if I launch N instances
of this image, what are the SO licensing implications? Will I have to
license/re-activate on each of the instances after they boot up?
On 01/23/2013 08:41 AM, Balamurugan V G wrote:
Hi,
I wonder how the Windows Licensing would work in OpenStack. Lets say I
have a Windows Image which I have already activated. Now if I launch N
instances of this image, what are the SO licensing implications? Will I
have to
I noticed that Grizzly-2 is in 13.04. I'd like to run them in 12.10 and not
update the entire OS.
What's the best and/or easiest way of doing this?
1) Get the source packages and build them in a PPA? If so, what is the
complete list of source packages and build order to do this correctly?
Hi Blair,
Without looking at the specific package versions you're after, the
intention of the Ubuntu Cloud Archive is to achieve exactly this goal. It's
really easy to use - check the Ubuntu wiki pages on it:
https://wiki.ubuntu.com/ServerTeam/CloudArchive
Regards,
Kev
On 23 January 2013
hi,
I search to add a floating ip address. I use quantum and not nova-network.
Can you help me ?
Thanks for your help
--
Cordialement,
Alexandre DE CARVALHO
___
Mailing list: https://launchpad.net/~openstack
Post to :
+1
On Wed, Jan 23, 2013 at 7:58 AM, Chris Behrens cbehr...@codestud.comwrote:
+1
On Jan 22, 2013, at 5:38 PM, Matt Dietz matt.di...@rackspace.com wrote:
All,
I think Trey Morris has been doing really well on reviews again, so
I'd
like to propose him to be reinstated for Nova
Hi all,
I took a look to the Nova blueprint [1] and I noticed that it depends on a
Quantum blueprint [2].
This blueprint [2] was created April 2012. Quantum is now able to
dynamically allocate ports and it's all Nova needs to implement this new
feature.
Can we obsoleted the Quantum blueprint [2]
Hello guys,
I'm installing the folsom version and I have one computer like the
controller and one being the compute node. I can start the VM with cirros
OS but I can't use the VNC, I got the error: Failed to connect to server
(code: 1006). I've been following this tutorial:
Hi Kevin,
Thanks for the link. It appears that my case is not explicitly supported,
running Folsom on 12.10 is only supported. I'll take a look when I'm on my
server, but if grizzly-2 packages are released for 12.04, then it'll be
possible to point my 12.10 system at the 12.04 repo and it
When i temporarily hard code the network_name variable in
/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py as below:
def _get_vif_infos():
vif_infos = []
for (network, mapping) in network_info:
mac_address = mapping['mac']
On 01/23/13 21:57, Guilherme Russi wrote:
Hello guys,
I'm installing the folsom version and I have one computer like the
controller and one being the compute node. I can start the VM with
cirros OS but I can't use the VNC, I got the error: Failed to connect
to server (code: 1006). I've
Ok,
I am no MS licensing expert, however. Here is my understanding of it.
If you are using a windows vm on a hypervisor other than windows server with
the Hyper-V role enabled you need to license per vm.
If you are using windows server with Hyper-V enable you can license at the
On 01/23/2013 06:34 AM, Trinath Somanchi wrote:
Hi Stackers-
I have installed glance and Keystone and configured them.
Not sure how you installed, but you need to make sure the PKI
provisioning is done. You can do it by hand with the keystone_manage
command. Make sure you run it as the
Hi all,
Thanks to Belmiro, I found how to fix this properly, rather than a hack.
For future googlers,
cd /etc/libvirt/nwfilter
cp nova-base.xml nova-base.xml.bak
virsh nwfilter-edit nova-base
remove or comment out the spoof lines you don't want
New instances won't have the rules.
To update
Thanks for the inputs everyone.
My concern is if the activation/licence key input needs to be done on each
VM after they boot up or its just as simple as having as many licences as
the VMs before hand and nothing needs to be done after the instance boots
up.
Regards,
Balu
On Wed, Jan 23, 2013
I've seen this question come up a couple times now; this error handling
here needs to be improved with a decent error message.
I opened a bug on the issue:
https://bugs.launchpad.net/keystone/+bug/1103569
-Dolph
On Wed, Jan 23, 2013 at 11:04 AM, Adam Young ayo...@redhat.com wrote:
On
Sounds like activation key management would be a great feature for the
Windows cloud-init so this could be passed in as meta data.
Tim
From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
[mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of
Balamurugan V
See
http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx
Looks like KMS would be the appropriate means; your MSFT reseller would sell
you a KMS license key to use for the appropriate pool of server / app
instances, then it is loaded into the KMS server, which
Site/Volume licensing works too. The KMS is there to enable/enforce the local
activiation/licensing.
The details of any licenses are also affected by the product sku’s that are
involved.
Peter J. Pouliot, CISSP
Senior SDET, OpenStack
Microsoft
New England Research Development Center
One
Hi
I have a running Essex OpenStack cluster on Ubuntu with multi host network
set up. Floating IP etc is working. I am planning to install same kind of
setup with Folsom on RHEL 6.3 and quantum. I have some questions
Most of the documents are mentioning quantum server with other nova
services
Hello,
I have just installed Folsom in a physical server, and the tenants can also
ping and ssh into each others instances.
I think there is something wrong with my setup.
Below I provide some info from the deployment.
Any tip will be very much appreciated.
Thanks.
Roni
nova-manage network
There is nothing wrong with your setup. L3 routing is done by the network node.
L3 is already blocked by security groups. The vlans provide L2 isolation.
Essentially we handle this with convention, as in tell your tenants not to open
up their firewalls if they don't want to be accessed by other
hello
I'm trying to use multi nics in essex, but it get an error:
ERROR: NoNetworksFound: No networks defined. (HTTP 400)
and this link https://bugs.launchpad.net/nova/+bug/953426 says that
essex currently not enable specific nics. and i tried to use that
patch in essex but failed.
I'm wondering
Hi-
Thanks for the help in replies.
I have installed keystone from the source code rather than the apt-get
command,
Kindly guide me on how to bring up keystone when installed from the source
code.
Thanking you all
-
Trinath
On Wed, Jan 23, 2013 at 10:34 PM, Adam Young ayo...@redhat.com
On 01/24/2013 12:02 AM, mohammad kashif wrote:
Hi
I have a running Essex OpenStack cluster on Ubuntu with multi host
network set up. Floating IP etc is working. I am planning to install
same kind of setup with Folsom on RHEL 6.3 and quantum. I have some
questions
Most of the documents
Hi,
I followed this instructions:
http://docs.openstack.org/essex/openstack-compute/admin/content/using-multi-nics.html
As I had already created the networks (nova-manage network create), I just
had to modify one of them to attach the second network to this project
(nova-manage network modify).
Hi,
I'm glad that you confirm my first impression about this blueprint :-) I'm
eager to help on this implementation, would you like me to rebase the
changes for you ? I can get to it right now.
Cheers,
Édouard.
On Wed, Jan 23, 2013 at 5:57 PM, heut2008 heut2...@gmail.com wrote:
I think we
at 20130123
Title: precise_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/83/Project:precise_grizzly_glance_trunkDate of build:Wed, 23 Jan 2013 12:18:15 -0500Build duration:9 min 2 secBuild cause:Started by user anonymousBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/226/Project:precise_grizzly_quantum_trunkDate of build:Wed, 23 Jan 2013 14:01:09 -0500Build duration:27 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/531/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 14:05:55 -0500Build duration:6 min 19 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_cinder_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_stable/140/Project:precise_folsom_cinder_stableDate of build:Wed, 23 Jan 2013 14:14:43 -0500Build duration:1 min 29 secBuild cause:Started by user anonymousBuilt
Title: precise_folsom_keystone_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_stable/85/Project:precise_folsom_keystone_stableDate of build:Wed, 23 Jan 2013 14:23:02 -0500Build duration:1 min 23 secBuild cause:Started by user
Title: precise_grizzly_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/227/Project:precise_grizzly_quantum_trunkDate of build:Wed, 23 Jan 2013 14:31:08 -0500Build duration:8 min 33 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/532/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 14:35:20 -0500Build duration:8 min 36 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_keystone_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_stable/86/Project:precise_folsom_keystone_stableDate of build:Wed, 23 Jan 2013 14:40:02 -0500Build duration:5 min 8 secBuild cause:Started by user
Title: quantal_folsom_keystone_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_stable/98/Project:quantal_folsom_keystone_stableDate of build:Wed, 23 Jan 2013 14:48:00 -0500Build duration:5 min 5 secBuild cause:Started by user
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/533/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 15:31:14 -0500Build duration:7 min 4 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/534/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 16:31:13 -0500Build duration:6 min 59 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/535/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 17:22:58 -0500Build duration:6 min 12 secBuild cause:Started by user anonymousBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/537/Project:precise_grizzly_nova_trunkDate of build:Wed, 23 Jan 2013 21:31:11 -0500Build duration:7 min 36 secBuild cause:Started by an SCM changeBuilt
55 matches
Mail list logo
