http://www.pubyun.com/blog/openstack/%E9%87%8D%E8%B4%9F%E8%BD%BD%E4%B8%8B%EF%BC%8Ckvm-%E7%BD%91%E7%BB%9C%E4%B8%AD%E6%96%AD%E7%9A%84%E9%97%AE%E9%A2%98/
check it. hope can solve your problem.
On Sat, Apr 13, 2013 at 5:30 PM, tommy(小包) bychya...@gmail.com wrote:
Hi stackers
we use
Hi,
i'm currently looking into deploying my first real (as in not local
devstack) OpenStack infrastructure and I intend to use Puppet to
automate things.
My questions is where can I find good modules for this purpose? I found
something on puppetforge but there doesn't seem to be any quantum
Hi guys
i've problem with my vnc console!! when i launch one instance, i can access
with ssh but i think it will be preferable to access with console!! but my vnc
still not working. message: fail to connect to server (novnc problem).
we installed novnc and vnc-consoleauth
here's the
VM's bridged connections are also good ... for both VM to VM and otherwise.
I have two compute nodes in my university and the network node and control
node are Virtual Box VM instances on my Laptop.
Regards,
Pranav
On Sat, Apr 13, 2013 at 12:34 AM, Steve Heistand steve.heist...@nasa.govwrote:
Hi all,
I joined this list just now to solve a particular problem, but once I'm past
this I hope to be giving back to the community.
I have spent the past week trying to get Keystone installed and configured
properly. I want to show a running OpenStack to my manager for a proof of
concept I
Hello,
There's also a mailing list for those modules if you need any help or would
like to help out:
https://groups.google.com/a/puppetlabs.com/forum/?fromgroups#!forum/puppet-openstack
They're a great set of modules with a great community behind them. Quantum
support is lacking at the moment,
It looks like you're doing everything correctly, except OS_PASSWORD is
*NOT* the same thing as the static admin_token in keystone.conf.
Passwords are user-specific attributes created using the --pass argument on
user-create for example. You may have set it to be the same as
keystone.conf's
Hi Mohammed,
This is unfortunately due the api-paste.ini needing to be updated after
upgrading to Grizzly. This is
due to the dot path for the v1 router being changed and not being
deprecated properly. There is a
bug [1] that is going to deprecate this properly, but for now you can just
copy the
Thanks Jeremy and Joe that is exactly what I was looking for!
Regards,
Dennis
On 13.04.2013 19:08, Joe Topjian wrote:
Hello,
There's also a mailing list for those modules if you need any help or
would like to help out:
Hi Dennis,
The modules mentioned above are in a great maintained state (just one known
issue related to nova_config that should be merged soon), and I hope to see
additional modules added for quantum and ceilometer added in the near
future.
I've heard reports that people have been happy with the
Hey Ralph,could you have a look at the two following files:/var/log/nova/novnc.log/var/log/nova/nova-consoleauth.logcheers!
Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15
Le 13 avr. 2013 à 14:39, Ralph lewis kale...@outlook.com a écrit :Hi guysi've problem with my vnc
On 2013-04-13, at 1:24 PM, Dolph Mathews dolph.math...@gmail.com wrote:
It looks like you're doing everything correctly, except OS_PASSWORD is *NOT*
the same thing as the static admin_token in keystone.conf.
You're right, actually. I DID use the admin_token for OS_PASSWORD. I'll
definitely be
On 2013-04-13, at 1:23 PM, Anne Gentle a...@openstack.org wrote:
Is this a regression or manifestation of this bug?
https://bugs.launchpad.net/keystone/+bug/1002917
Anne
I'll take a look at that bug. I currently don't have the depth of knowledge on
OpenStack to judge myself, but maybe
I was running Folsom on Quantal with nova-network using a
FlatDHCPManager and upgraded to Raring today, which upgrades to Grizzly.
After working through config files, trying to launch a 12.04.2 LTS
instance, the VM console log shows:
Begin: Running /scripts/init-bottom ... done.
[
On 2013-04-13, at 5:24 PM, Dolph Mathews dolph.math...@gmail.com wrote:
Hmm, well it looks like you already have debug enabled, which is indicating
that the username + password combination is bad (if debug was disabled, you'd
get a much more opaque error message). The tenant name you
On Sun, Mar 31, 2013 at 10:22 PM, Balamurugan V G
balamuruga...@gmail.comwrote:
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?
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with 192.168.1.2 but it should be
with 192.168.2.2. There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the 192.168.1.2 address?
I disabled the DHCP server on
On 04/13/2013 03:29 PM, Blair Zajac wrote:
On 04/13/2013 03:07 PM, Blair Zajac wrote:
The ci-info lines show it coming up with 192.168.1.2 but it should be
with 192.168.2.2. There's a router providing DHCP on the network that
the host is on, so maybe that's where it's getting the 192.168.1.2
--vncserver_proxyclient_address=127.0.0.1
--vncserver_listen=127.0.0.1
are you sure about these two Ip addresses?
Regards,
Pranav
On Sun, Apr 14, 2013 at 12:36 AM, Razique Mahroua razique.mahr...@gmail.com
wrote:
Hey Ralph,
could you have a look at the two following files:
at 20130413-2103Build needed 00:00:41, 15152k disc
Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/71/Project:precise_havana_nova_trunkDate of build:Sun, 14 Apr 2013 00:31:39 -0400Build duration:42 secBuild cause:Started by an SCM changeBuilt
21 matches
Mail list logo
