Re: [Openstack] What is the correct config for vnc or novnc tosuccessfully enable VNC CONSOLE in a browser?

[Anthony Young]

See below:

>
> but I get some thing strange for:
> if I set
> --vnc_enabled=true
> --novncproxy_base_url=http://localhost:6080/vnc_auto.html
> --vncserver_proxyclient_address=localhost
> --vncserver_listen=0.0.0.0
> in nova.conf that it return
> Oops! Google Chrome could not connect to 
> localhost:6080
>
> in dashboard,but work fine when I use command *nova get-vnc-console demo
> novnc  ..*It return a url as
> http://localhost:6080/vnc_auto.html?token=XX..
> then I enter this url in chrome with
> http://172.18.187.110:6080/vnc_auto.html?token=XX
> ps:172.18.187.110 is the public ip of my openstack server..
> *It can return my VM's screen ..*
> *
> *
> however,when I set
> --vnc_enabled=true
> --novncproxy_base_url=http://172.18.187.110:6080/vnc_auto.html
> --vncserver_proxyclient_address=172.18.187.110
> --vncserver_listen=0.0.0.0
>
> and restart all the services ..
> both dashboard and url from command *nova get-vnc-console demo novnc *returns
> server connot connect
> **
>
> *I am wondering how would localhost and 172.18.187.110 be not the same???*
> *
> *
>


If you launched this instance before you specified --vncserver_listen, then
the instance's vnc server will bind 127.0.0.1.  Furthermore, this
configuration will be baked into the instances libvirt.xml file, so changes
to --vncserver_listen in your nova.conf will not have any effect for
already existing instances.

Did you happen to launch this instance before you set --vncserver_listen to
0.0.0.0?  If so, you may try to launch another instance and see if vnc is
working properly.

Just for the record, --vncserver_listen is generally set to the hosts
management ip, rather than the public ip or 0.0.0.0, for security reasons.


> **
> thanks
>
> dming
>
> -- Original --
> *From: * "Kiall Mac Innes";
> *Date: * Sat, Apr 7, 2012 07:15 PM
> *To: * "Eric Luo";**
> *Cc: * "openstack";**
> *Subject: * Re: [Openstack] What is the correct config for vnc or novnc
> tosuccessfully enable VNC CONSOLE in a browser?
>
> For anyone else who might be hng the same issue.. These two packages,
> combined with these options will get novnc working on precise..
>
> --vnc_enabled=true
> --novncproxy_base_url=http://78.153.XXX.XXX:6080/vnc_auto.html
> --vncserver_proxyclient_address=78.153.XXX.XXX
> --vncserver_listen=0.0.0.0
>
> I've intentionally kept the version numbers identical to the packages
> currently in the precise repo's. This will hopefully let apt "do the right
> thing" once an official update is released..
>
> http://dl.dropbox.com/u/1400487/novnc_2012.1~e3%2Bdfsg-1_amd64.deb
>
> http://dl.dropbox.com/u/1400487/python-novnc_2012.1~e3%2Bdfsg-1_all.deb
>
> Thanks,
> Kiall
>
>
> On Sat, Apr 7, 2012 at 11:14 AM, Kiall Mac Innes 
>  wrote:
>
>> The novnc package included in 12.04 is outdated/broken.
>>
>> I know Chuck is planning to fix it ASAP..
>>
>> In the meantime, I hacked together a fixed .deb.. I can stick it
>> somewhere for you to download if you like?
>>
>> Thanks,
>> Kiall
>>
>> Sent from my phone.
>> On Apr 7, 2012 9:31 a.m., "Eric Luo"  wrote:
>>
>>> Hello ,all
>>> I installed Openstack as a all-in-one solution ,I got everything runs
>>> correctly ,I can ssh to my VMs etc. But there is a problem here: I can not
>>> use the VNC tag in dashboard.
>>> I have installed the nova-consoleauth and novnc by "apt-get" .but I can
>>> not statrt the nova-novncproxy service (by the way ,the nova-vncproxy
>>> service always runs OK),
>>> When I use the command root@ubuntu:~# *service novnc start*
>>> I got the following with nothing else:
>>> * Starting OpenStack NoVNC proxy nova-novncproxy
>>>
>>> It only says "starting",but does not say "started"!
>>>
>>> actually it is not started ,by command *service novnc status, *it says:
>>> * nova-novncproxy is not running.
>>>
>>> when I use command *nova-novncproxy --flagfile=/etc/nova/nova.conf* ,I
>>> got the following:
>>>
>>> WARNING: no 'numpy' module, HyBi protocol support disabled
>>> Traceback (most recent call last):
>>> File "/usr/bin/nova-novncproxy", line 40, in 
>>> flags.DEFINE_boolean('verbose', False,
>>> AttributeError: 'module' object has no attribute 'DEFINE_boolean'
>>>
>>> When I use command *nova get-vnc-console testVM novnc*
>>>
>>>
>>>
>>> +---++
>>> | Type | Url |
>>>
>>> +---++
>>> | novnc |
>>> http://192.168.0.202:6080/vnc_auto.html?token=e1095862-deb9-4cb5-9ec9-44aa0200342e
>>>  |
>>>
>>> +---++
>>>
>>> but When pasted the url above into my chrome ,I got the following :
>>> Oops! Google Chrome could not connect to 192.168.0.202:

Re: [Openstack] Melange Unittests

[Vaze, Mandar]

Commenting line 32-EOF from setup.cfg didn't help
I also pip installed openstack.nose_plugin - still didn't help

Even if I try to run single test module, I still see same error(s) e.g. "python 
run_tests.py unit.test_ipam_models"
I run these from /opt/stack/mélange

Here are the actual/detailed errors I see :

==
ERROR: 
--
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/nose/suite.py", line 208, in run
self.setUp()
  File "/usr/lib/pymodules/python2.7/nose/suite.py", line 291, in setUp
self.setupContext(ancestor)
  File "/usr/lib/pymodules/python2.7/nose/suite.py", line 314, in setupContext
try_run(context, names)
  File "/usr/lib/pymodules/python2.7/nose/util.py", line 478, in try_run
return func()
  File "/opt/stack/melange/melange/tests/functional/__init__.py", line 32, in 
setup
db_api.db_reset(conf, db_based_ip_generator, db_based_mac_generator)
  File "/opt/stack/melange/melange/db/sqlalchemy/api.py", line 259, in db_reset
db_sync(options)
  File "/opt/stack/melange/melange/db/sqlalchemy/api.py", line 246, in db_sync
migration.db_sync(options, version, repo_path)
  File "/opt/stack/melange/melange/db/sqlalchemy/migration.py", line 124, in 
db_sync
upgrade(options, version=version, repo_path=repo_path)
  File "/opt/stack/melange/melange/db/sqlalchemy/migration.py", line 66, in 
upgrade
return versioning_api.upgrade(sql_connection, repo_path, version)
  File "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186, 
in upgrade
return _migrate(url, repository, version, upgrade=True, err=err, **opts)
  File "", line 2, in _migrate
  File "/usr/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py", 
line 159, in with_engine
return f(*a, **kw)
  File "/usr/lib/python2.7/dist-packages/migrate/versioning/api.py", line 365, 
in _migrate
schema.runchange(ver, change, changeset.step)
  File "/usr/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 
91, in runchange
change.run(self.engine, step)
  File "/usr/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line 
145, in run
script_func(engine)
  File 
"/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py",
 line 29, in upgrade
_db_connect()
  File 
"/opt/stack/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py",
 line 62, in _db_connect
conf, app = config.Config.load_paste_app('melange', options, args)
  File "/opt/stack/melange/melange/common/config.py", line 37, in load_paste_app
conf, app = openstack_config.load_paste_app(*args, **kwargs)
  File "/opt/stack/melange/melange/openstack/common/config.py", line 283, in 
load_paste_app
args, config_dir)
  File "/opt/stack/melange/melange/openstack/common/config.py", line 252, in 
load_paste_config
"Cannot load application %s" % app_name)
RuntimeError: Unable to locate any configuration file. Cannot load application 
mélange


-Mandar


-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On 
Behalf Of Jason Kölker
Sent: Friday, April 06, 2012 8:21 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Melange Unittests

On Fri, 2012-04-06 at 13:11 +, Vaze, Mandar wrote:
> I tried to run ./run_tests.sh (without virtualenv) I kept on getting error 
> related to "unable to find config file"
> I ran the tests from /opt/stack/mélange Same errors when I run "python 
> run_tests.py"
> /opt/stack/mélange/etc/mélange/mélange.conf is present and valid.
> 
> How do I pass the config file to run_tests ? (Shouldn't it pick it up 
> automatically)

The nova test runner is busted. We had converted it to use tox, but as 
Brian/James has found out there is an issue with the openstack.nose_plugin and 
something in melange causing tests to not be picked up by the collector.

For the time being edit setup.cfg and comment out lines 32-EOF. Since melange 
is merging with quantum, my plan is to fix them as I merge them into the 
quantum tests.

Happy Hacking!

7-11


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding

[Openstack] [OpenStack] boot from iso image

[William Herry]

Hi

I am try the openstack's new feature of boot from iso image, and after
installation it boot up a working system, it is really awesome

but I have a little question is that, I give 10G disk when i create this
instance but during the installation and after boot up, I got almost 20G,
what's going on here? did i miss configure some, I am use essex rc1

Thanks

-- 

===
William Herry

williamherrych...@gmail.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

[Openstack] anybody have a machine named rudger.drecomm?

[Monty Taylor]

Hello all!

Someone has spun up a nice new node using the puppet modules that we use
for OpenStack CI. That's GREAT - and I'm thrilled that you're finding
things useful. You're also helped us notice a bug/design flaw though in
one of our modules. The configuration of where to send sysadmin email is
baked in too far down into the puppet module. We've refactored that now
so that it's a parameter ... so that if you use our modules to spin up a
test server, you won't get one that is configured to send _us_ email
when cron jobs fail. :)

In the mean time though, if you're the person who spun the node up,
please ping us so we can talk about getting a change applied to your node...

Monty

___
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] OpenStack Plugin for Jenkins

[Monty Taylor]

On 04/05/2012 01:22 AM, Justin Santa Barbara wrote:
> I've got Compute functionality working with the OpenStack Jenkins
> plugin, so it can launch nova instances as on-demand slaves now, run
> builds on them, and archive the results into  swift.  I'd like to open
> GitHub issues to track your requirements, but I have a few questions.

I shall do my best to elaborate...

>> We need disposable machines that are only used for one test, which
> means spinning up and terminating hundreds of machines per day.
> 
> Sounds like we want a function to terminate the machine after the job
> has run.
> https://github.com/platformlayer/openstack-jenkins/issues/1

Yes. That seems sensible.

>> We need to use machines from multiple providers simultaneously so that
> we're resilient against errors with one provider.
> 
> Label expressions should work here; you would apply a full set of axis
> labels to each machine ("rax oneiric python26") but then you would
> filter based only on the required axes ("oneric python26").  Are labels
> sufficient for this?

Labels are sufficient for tying the jobs to the specific resource
description. I think the idea here is that we definitely want to be able
to configure multiple cloud providers, and for each provider (in some
manner) be able to configure what a machine labeled "oneiric" would look
like. (likely as a combination of image, flavor and setup script)

After that - honestly - as long as we can actually get an "oneiric"
labeled machine from _someone_ when we ask for it, we're good.

>> We need to pull nodes from a pool of machines that have been spun up
> ahead of time for speed.
> 
> This sounds like a custom NodeProvisioner implementation.  The current
> implementation is optimized around minimizing CPU hours, by doing load
> prediction.  You have a different criteria, based on minimizing launch
> latency.  It looks like it should be relatively easy to implement a new
> algorithm, although perhaps a bit tricky to figure out how to plug it in.
> 
> https://github.com/platformlayer/openstack-jenkins/issues/2

Yeah - average time to spin up a node and get it configured
_when_it_works_ is between 5 and 10 minutes. devstack takes around that
amount of time, so if we have to actually wait for the node to spin up
each time, we'd be doubling the time it takes to test a change.

Then there's the fact that clouds fail at giving us working node ALL THE
TIME. So waiting for re-trys and such (although if it was happening at
jenkins node provisioning time would be technically correct) could
potentially lead to a terribly build queue!

> 
>> We need to be able to select from different kinds of images for
> certain tests.
> 
> Are labels sufficient for this?

Yes. Configuring the characteristics of an image and assigning a label
to those characteristics will definitely let us associate tests with the
right running environment.

>> Machines need to be checked for basic functionality before being added
> to the pool (we frequently get nodes without a functioning network).
> 
> I believe Jenkins does this anyway; a node which doesn't have networking
> won't be able to get the agent.  And you can run your own scripts after
> the slave boots up ("apt-get install openjdk", for example).  Those
> scripts can basically do any checks you want.  Is that enough?

Yes- just pointing out that it's a case that we have to deal with at the
moment so it needs to be handled.

>> They need to be started from snapshots with cached data on them to
> avoid false negatives from network problems.
> 
> Can you explain this a bit more?  This is to protect against the apt
> repositories / python sources / github repos being down?  Would an http
> proxy be enough?

Yes. apt repositories, pypi and github are CONSTANTLY down, so we do a
lot of work to pre-cache network fetched resources onto a machine so
that running of the tests almost never have to involve a network fetch.
(we've learned over the last year or so that any time a test system
wants to fetch network resources, that the number of false-negatives due
to github or pypi going away is unworkably high)

It's possible that an http proxy _might_ help that - but the approach
we've been taking so far is to have one process that spins up a node,
does all the network fetching into local resources, and then snapshots
that into an image which is the basis for subsequent node creation. The
base image is updated nightly so that the amount of network update that
has to happen at node instantiation time is minimized.

jclouds itself (rather than the plugin) has a caching feature which does
the auto-image creation based on node creation criteria. So if you
combine the characteristics of a node (image, flavor, init-script, ram,
volumes, etc) with a TTL, then the first time a node meeting those
criteria is requested, it will create you one from scratch, but at the
end of the user data script run, it will create an image snapshot which
it can use for subsequent creation of node

Re: [Openstack] Spelling error on www.openstack.org

[Michael Still]

On 09/04/12 14:18, Todd Morey wrote:

> Mikal, are you running Essex? It already has them. (See release notes
> under "World Domination Enhancements".)

Careful now. The release notes are a wiki, and you might end up with a
World Domination section...

Mikal


___
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] Image API v2 Draft 4

[Brian Waldon]

The next draft of the v2 OpenStack Image API is available for review:

https://docs.google.com/document/d/1rb7ZVn0Du_5NZqUyQpqUZSmv7Qd66TMHYAtvsow7LH4/edit.
 

Unfortunately, there won't be time for an official session at the summit, but 
feel free to start a discussion through email or by using the comment system in 
the doc itself. I'll also be available at the summit to discuss this in an 
unofficial capacity. There are still a few kinks to work out, but we're finally 
getting started implementing this thing. Thanks to everyone who has helped out 
so far!

Brian Waldon


APPENDIX A: Major Changes From Draft 3

1) Removed concept of image locations - Replication and multiple image 
locations are not yet well-formed. It's unclear what information/capabilities 
we need in the API at the moment, so I've simplified it down to just GET 
/images//file. I would prefer to keep the public-facing API as simple 
as possible, so maybe this belongs in an Admin-only API. We can iterate on this 
for the next 6 months if we need to…

2) Replaced access_type with visibility - Rather than 'public', 'private' and 
'shared', visibility can be either 'public' or 'private'. Added some 
explanation of how 'visibility' plays with 'owner' in the concepts section of 
the doc.


APPENDIX B: Outstanding issues

Some of this stuff is hard, some I just haven't put the time into figuring out 
yet:

1) Does it make sense to use tags, metadata, or both? I can see cases for both, 
but is that overkill?

2) How do we fit the existing 'copy_from' functionality in?

3) Need to properly convey link objects in json schemas

4) Need to write xsds :(

5) What link relation do we use for subcollections like tags, access, etc? 
http://www.iana.org/assignments/link-relations/link-relations.xml___
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] Nova Extension Docs

[Brian Waldon]

We all know developers don't love writing docs, and when it isn't easy it won't 
get done. Unfortunately, that now means that we've shipped Essex without 
appropriate documentation of our API extensions. We could really use some help 
catching back up and getting these docs written, so if you've got 20 minutes to 
spare, head over to http://etherpad.openstack.org/nova-ext-docs and help us out!

Thanks!
Brian Waldon___
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] [Ops] OpenStack and Operations: Input from the Wild

[Huang Zhiteng]

Hi Tim,

Could you elaborate more on 'performance metrics'?  Like what kind of
metrics are considered as performance ones?  Thanks.

On Sat, Apr 7, 2012 at 2:13 AM, Tim Bell  wrote:

> ** **
>
> Splitting monitoring into
>
> ** **
>
> **1.   **Gathering of metrics (availability, performance) and
> reporting in a standard fashion should be part of OpenStack. 
>
> **2.   **Best practice sensors should sample the metrics and provide
> alarms for issues which could cause service impacts. Posting of these
> alarms to a monitoring system should be based on plug ins
>
> **3.   **Reference implementations for standard monitoring systems
> such as Nagios should be available that queries the data above and feeds it
> into the package selected
>
> ** **
>
> Each site does not want to be involved in defining the best practice.
> Equally, each monitoring system should not have to have an intimate
> understanding of OpenStack to produce a red/green light.  The components
> for 1 and 2 fall under the associated openstack component. Component 3 is
> the monitoring solution provider.
>
> ** **
>
> Tim
>
> ** **
>
> *From:* openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:
> openstack-bounces+tim.bell=cern...@lists.launchpad.net] *On Behalf Of *David
> Kranz
> *Sent:* 06 April 2012 16:44
> *To:* Andrew Clay Shafer
> *Cc:* openstack-operat...@lists.openstack.org; openstack; Duncan McGreggor
> *Subject:* Re: [Openstack] [Ops] OpenStack and Operations: Input from the
> Wild
>
> ** **
>
> This is a really great list! With regard to cluster health and monitoring,
> I did a bunch of stuff with Swift before turning to nova and really
> appreciated the
> way each swift service has a "healthcheck" call that can be used by a
> monitoring system. While I don't think providing a production-ready
> monitoring system should be part of core OpenStack, it is the core
> architects who really know what needs to be checked to ensure that a system
> is healthy. There are various sets of poking at ports, process lists and so
> on that Crowbar, Zenoss, etc. set up but it would be a big improvement for
> deployers if each openstack service provided healthcheck apis based on
> expert knowledge of what is supposed to be happening inside. That would
> also insulate deployers from changes in the code that might impact what it
> means to be running properly. Looking forward to the discussion.
>
>  -David
>
>
>
> On 4/6/2012 1:06 AM, Andrew Clay Shafer wrote: 
>
> Interested in devops.
>
> ** **
>
> Off the top of my head.
>
> ** **
>
> live upgrades
>
> api queryable indications of cluster health
>
> api queryable cluster version and configuration info
>
> enabling monitoring as a first class concern in OpenStack (either as a
> cross cutting concern, or as it's own project)
>
> a framework for gathering and sharing performance benchmarks with
> architecture and configuration
>
> ** **
>
> ** **
>
> On Thu, Apr 5, 2012 at 1:52 PM, Duncan McGreggor 
> wrote:
>
> For anyone interested in DevOps, Ops, cloud hosting management, etc.,
> there's a proposed session we could use your feedback on for topics of
> discussion:
>  http://summit.openstack.org/sessions/view/57
>
> Respond with your thoughts and ideas, and I'll be sure to add them to the
> list.
>
> Thanks!
>
> d
>
> ___
> 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
>
> ** **
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Regards
Huang Zhiteng
___
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] Spelling error on www.openstack.org

[Michael Still]

On 09/04/12 11:07, Mark Collier wrote:
> Todd morey (t...@openstack.org) is your friendly neighborhood webmaster and 
> laser operator.

Todd, can I please have a laser too?

> Michael Still  wrote:
> 
> I'm not sure who to report this to, but I just noticed that the yellow
> graphic at the top left of www.openstack.org proudly announces that
> essex was "relased" recently.
> 
> I hope it develops laser based super powers. That would be cool.
> 
> Mikal

Thanks,
Mikal

___
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] Jcloud and openstack relation

[Monty Taylor]

Yes - jclouds and OpenStack Java are both bindings to be used to launch
and orchestrate cloud instances. Neither are aimed at running Java in
any particular way inside of a cloud instance. Honestly, I don't see any
reason that normal jvms shouldn't work just fine in a cloud server.

On 04/08/2012 07:24 PM, Frans Thamura wrote:
> hi
> 
> i see jclouds it is like binding, right... 
> 
> but should we launch a Java apps, which Java under JVM and
> Cloud/Virtualization also in Cloud, why dont auto launch
> 
> i see JRockit VE run good in VMWare (i saw it 2007).
> 
> F
> 
> On Mon, Apr 9, 2012 at 9:21 AM, Justin Santa Barbara
> mailto:jus...@fathomdb.com>> wrote:
> 
> There is also a (friendly rival) OpenStack Java binding being developed:
> https://github.com/platformlayer/openstack-java
> https://github.com/woorea/openstack-java-sdk/
> 
> That library supports a direct-to-OpenStack Jenkins plugin which I
> confidently predict will rapidly surpass any
> lowest-common-denominator attempts (*):
> https://github.com/platformlayer/openstack-jenkins
> 
> (*: This opinion may be biased)
> 
> If you do evaluate JClouds against the OpenStack Java bindings (or
> the Jenkins plugin), please let me know of any areas where the
> OpenStack bindings aren't better, and I will make sure to improve
> that area.
> 
> Monty: We should port the OpenStack CI team's work to the OpenStack
> Jenkins plugin at the summit!
> 
> Justin
> 
> 
> 
> 
> On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor  > wrote:
> 
> Hi!
> 
> jclouds is an open source java library for connecting to clouds. As
> such, it supports connecting to OpenStack based clouds. The
> OpenStack CI
> team have been working with jclouds on both support for OpenStack as
> well as a plugin for jenkins so that we can have more direct
> control of
> build slaves on the clouds we use for that purpose.
> 
> Does that help?
> 
> Monty
> 
> On 04/07/2012 07:02 PM, Frans Thamura wrote:
> > hi all
> >
> > can share to me, what is the relateion between openstack and
> jclouds.
> >
> > F
> >
> >
> > ___
> > 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
> 
> 
> 

___
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] Jcloud and openstack relation

[Monty Taylor]

On 04/08/2012 07:21 PM, Justin Santa Barbara wrote:
> There is also a (friendly rival) OpenStack Java binding being developed:
> https://github.com/platformlayer/openstack-java
> https://github.com/woorea/openstack-java-sdk/

Friendly rivalries are the best!

> That library supports a direct-to-OpenStack Jenkins plugin which I
> confidently predict will rapidly surpass any lowest-common-denominator
> attempts (*):
> https://github.com/platformlayer/openstack-jenkins
> 
> (*: This opinion may be biased)
> 
> If you do evaluate JClouds against the OpenStack Java bindings (or the
> Jenkins plugin), please let me know of any areas where the OpenStack
> bindings aren't better, and I will make sure to improve that area.

I'd say the same applies in the reverse, too. If we cross-file bugs
against each project, both should eventually rule the world.

> Monty: We should port the OpenStack CI team's work to the OpenStack
> Jenkins plugin at the summit!

Justin - I definitely want to sit down with you and Adrian Cole at the
summit... the more we chat about usecases and whatnot the better
everyone winds up being, I think. One of the things we're trying to do
is provide a happy migration path for folks - but you know - face to
face about this stuff often winds up being super-big win.

Yay for Open Source!

Monty

> On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor  > wrote:
> 
> Hi!
> 
> jclouds is an open source java library for connecting to clouds. As
> such, it supports connecting to OpenStack based clouds. The OpenStack CI
> team have been working with jclouds on both support for OpenStack as
> well as a plugin for jenkins so that we can have more direct control of
> build slaves on the clouds we use for that purpose.
> 
> Does that help?
> 
> Monty
> 
> On 04/07/2012 07:02 PM, Frans Thamura wrote:
> > hi all
> >
> > can share to me, what is the relateion between openstack and jclouds.
> >
> > F
> >
> >
> > ___
> > 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
> 
> 

___
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] Jcloud and openstack relation

[Frans Thamura]

hi

i see jclouds it is like binding, right...

but should we launch a Java apps, which Java under JVM and
Cloud/Virtualization also in Cloud, why dont auto launch

i see JRockit VE run good in VMWare (i saw it 2007).

F

On Mon, Apr 9, 2012 at 9:21 AM, Justin Santa Barbara wrote:

> There is also a (friendly rival) OpenStack Java binding being developed:
> https://github.com/platformlayer/openstack-java
> https://github.com/woorea/openstack-java-sdk/
>
> That library supports a direct-to-OpenStack Jenkins plugin which I
> confidently predict will rapidly surpass any lowest-common-denominator
> attempts (*):
> https://github.com/platformlayer/openstack-jenkins
>
> (*: This opinion may be biased)
>
> If you do evaluate JClouds against the OpenStack Java bindings (or the
> Jenkins plugin), please let me know of any areas where the OpenStack
> bindings aren't better, and I will make sure to improve that area.
>
> Monty: We should port the OpenStack CI team's work to the OpenStack
> Jenkins plugin at the summit!
>
> Justin
>
>
>
>
> On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor  wrote:
>
>> Hi!
>>
>> jclouds is an open source java library for connecting to clouds. As
>> such, it supports connecting to OpenStack based clouds. The OpenStack CI
>> team have been working with jclouds on both support for OpenStack as
>> well as a plugin for jenkins so that we can have more direct control of
>> build slaves on the clouds we use for that purpose.
>>
>> Does that help?
>>
>> Monty
>>
>> On 04/07/2012 07:02 PM, Frans Thamura wrote:
>> > hi all
>> >
>> > can share to me, what is the relateion between openstack and jclouds.
>> >
>> > F
>> >
>> >
>> > ___
>> > 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
>>
>
>
___
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] Jcloud and openstack relation

[Justin Santa Barbara]

There is also a (friendly rival) OpenStack Java binding being developed:
https://github.com/platformlayer/openstack-java
https://github.com/woorea/openstack-java-sdk/

That library supports a direct-to-OpenStack Jenkins plugin which I
confidently predict will rapidly surpass any lowest-common-denominator
attempts (*):
https://github.com/platformlayer/openstack-jenkins

(*: This opinion may be biased)

If you do evaluate JClouds against the OpenStack Java bindings (or the
Jenkins plugin), please let me know of any areas where the OpenStack
bindings aren't better, and I will make sure to improve that area.

Monty: We should port the OpenStack CI team's work to the OpenStack Jenkins
plugin at the summit!

Justin



On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor  wrote:

> Hi!
>
> jclouds is an open source java library for connecting to clouds. As
> such, it supports connecting to OpenStack based clouds. The OpenStack CI
> team have been working with jclouds on both support for OpenStack as
> well as a plugin for jenkins so that we can have more direct control of
> build slaves on the clouds we use for that purpose.
>
> Does that help?
>
> Monty
>
> On 04/07/2012 07:02 PM, Frans Thamura wrote:
> > hi all
> >
> > can share to me, what is the relateion between openstack and jclouds.
> >
> > F
> >
> >
> > ___
> > 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
>
___
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] Jcloud and openstack relation

[Monty Taylor]

Hi!

jclouds is an open source java library for connecting to clouds. As
such, it supports connecting to OpenStack based clouds. The OpenStack CI
team have been working with jclouds on both support for OpenStack as
well as a plugin for jenkins so that we can have more direct control of
build slaves on the clouds we use for that purpose.

Does that help?

Monty

On 04/07/2012 07:02 PM, Frans Thamura wrote:
> hi all
> 
> can share to me, what is the relateion between openstack and jclouds.
> 
> F
> 
> 
> ___
> 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

Re: [Openstack] Spelling error on www.openstack.org

[Mark Collier]

Todd morey (t...@openstack.org) is your friendly neighborhood webmaster and 
laser operator.



Michael Still  wrote:


I'm not sure who to report this to, but I just noticed that the yellow
graphic at the top left of www.openstack.org proudly announces that
essex was "relased" recently.

I hope it develops laser based super powers. That would be cool.

Mikal

___
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

[Openstack] Spelling error on www.openstack.org

[Michael Still]

I'm not sure who to report this to, but I just noticed that the yellow
graphic at the top left of www.openstack.org proudly announces that
essex was "relased" recently.

I hope it develops laser based super powers. That would be cool.

Mikal

___
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] mock, mox, stubs, fakes, etc

[Joseph Heck]

Thanks Lorin! That helps me quite a bit.

-joe

On Apr 8, 2012, at 3:20 PM, Lorin Hochstein wrote:

> mox and mock are two competing Python libraries for defining mock objects for 
> unit tests. I think they're basically equivalent in terms of what you can do 
> with them, but they use different styles: In mox the assertions are written 
> before the code under test, and in mock the assertions are written after the 
> code under test. 
> 
> I personally think mock is more Pythonic, and it's what I use on other 
> projects. Mox is a port of a Java library, and mock was (AFAIK) written 
> specifically for Python. Also, Mock has been accepted into the Python 3.3(?) 
> standard library as a submodule of unit tests. However, mox has been the main 
> mocking library used in Nova unit test for as long as I have been familiar 
> with the code.
> 
> Take care,
> 
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
> 
> 
> 
> 
> 
> On Apr 8, 2012, at 4:06 PM, Joseph Heck wrote:
> 
>> Poking around through all various mechanisms we have to test and verify 
>> OpenStack - does anyone have a concise writeup on the various tools and 
>> techniques that we're using? 
>> 
>> I'm not familiar with the "stubs" or "mock" libraries, and a little familiar 
>> with mox.
>> 
>> Is anyone who is familiar with them all willing to take a stab at outlining 
>> where they're individually most effective and useful?
>> 
>> -joe
>> 
>> ___
>> 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

Re: [Openstack] mock, mox, stubs, fakes, etc

[Lorin Hochstein]

mox and mock are two competing Python libraries for defining mock objects for 
unit tests. I think they're basically equivalent in terms of what you can do 
with them, but they use different styles: In mox the assertions are written 
before the code under test, and in mock the assertions are written after the 
code under test. 

I personally think mock is more Pythonic, and it's what I use on other 
projects. Mox is a port of a Java library, and mock was (AFAIK) written 
specifically for Python. Also, Mock has been accepted into the Python 3.3(?) 
standard library as a submodule of unit tests. However, mox has been the main 
mocking library used in Nova unit test for as long as I have been familiar with 
the code.

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





On Apr 8, 2012, at 4:06 PM, Joseph Heck wrote:

> Poking around through all various mechanisms we have to test and verify 
> OpenStack - does anyone have a concise writeup on the various tools and 
> techniques that we're using? 
> 
> I'm not familiar with the "stubs" or "mock" libraries, and a little familiar 
> with mox.
> 
> Is anyone who is familiar with them all willing to take a stab at outlining 
> where they're individually most effective and useful?
> 
> -joe
> 
> ___
> 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

[Openstack] mock, mox, stubs, fakes, etc

[Joseph Heck]

Poking around through all various mechanisms we have to test and verify 
OpenStack - does anyone have a concise writeup on the various tools and 
techniques that we're using? 

I'm not familiar with the "stubs" or "mock" libraries, and a little familiar 
with mox.

Is anyone who is familiar with them all willing to take a stab at outlining 
where they're individually most effective and useful?

-joe

___
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] What is the correct config for vnc or novnc tosuccessfully enable VNC CONSOLE in a browser?

[.。o 0 O泡泡]

thanks kiall


with your two packages that novnc work fine .


but I get some thing strange for:
if I set 
--vnc_enabled=true

--novncproxy_base_url=http://localhost:6080/vnc_auto.html
--vncserver_proxyclient_address=localhost

--vncserver_listen=0.0.0.0
in nova.conf that it return 

Oops! Google Chrome could not connect to localhost:6080 
in dashboard,but work fine when I use command nova get-vnc-console demo novnc  
..It return a url as http://localhost:6080/vnc_auto.html?token=XX..
then I enter this url in chrome with 
http://172.18.187.110:6080/vnc_auto.html?token=XX 
ps:172.18.187.110 is the public ip of my openstack server..
It can return my VM's screen ..


however,when I set
--vnc_enabled=true

--novncproxy_base_url=http://172.18.187.110:6080/vnc_auto.html
--vncserver_proxyclient_address=172.18.187.110

--vncserver_listen=0.0.0.0



and restart all the services ..
both dashboard and url from command nova get-vnc-console demo novnc returns 
server connot connect
 
I am wondering how would localhost and 172.18.187.110 be not the same???


thanks


dming
 
-- Original --
From:  "Kiall Mac Innes";
Date:  Sat, Apr 7, 2012 07:15 PM
To:  "Eric Luo";
Cc:  "openstack";
Subject:  Re: [Openstack] What is the correct config for vnc or novnc 
tosuccessfully enable VNC CONSOLE in a browser?

 
For anyone else who might be hng the same issue.. These two packages, combined 
with these options will get novnc working on precise..

--vnc_enabled=true
--novncproxy_base_url=http://78.153.XXX.XXX:6080/vnc_auto.html
--vncserver_proxyclient_address=78.153.XXX.XXX
--vncserver_listen=0.0.0.0


I've intentionally kept the version numbers identical to the packages currently 
in the precise repo's. This will hopefully let apt "do the right thing" once an 
official update is released..


http://dl.dropbox.com/u/1400487/novnc_2012.1~e3%2Bdfsg-1_amd64.deb


http://dl.dropbox.com/u/1400487/python-novnc_2012.1~e3%2Bdfsg-1_all.deb 

Thanks,
Kiall


On Sat, Apr 7, 2012 at 11:14 AM, Kiall Mac Innes  wrote:

The novnc package included in 12.04 is outdated/broken.

I know Chuck is planning to fix it ASAP..

In the meantime, I hacked together a fixed .deb.. I can stick it somewhere for 
you to download if you like?


Thanks,
Kiall

Sent from my phone.
On Apr 7, 2012 9:31 a.m., "Eric Luo"  wrote:


Hello ,allI installed Openstack as a all-in-one solution ,I got everything runs 
correctly ,I can ssh to my VMs etc. But there is a problem here: I can not use 
the VNC tag in dashboard.
I have installed the nova-consoleauth and novnc by "apt-get" .but I can not 
statrt the nova-novncproxy service (by the way ,the nova-vncproxy service 
always runs OK),
When I use the command root@ubuntu:~# service novnc start
I got the following with nothing else:
* Starting OpenStack NoVNC proxy nova-novncproxy


It only says "starting",but does not say "started"!


actually it is not started ,by command service novnc status, it says: * 
nova-novncproxy is not running.


when I use command nova-novncproxy --flagfile=/etc/nova/nova.conf ,I got the 
following:


WARNING: no 'numpy' module, HyBi protocol support disabled
Traceback (most recent call last):
File "/usr/bin/nova-novncproxy", line 40, in 
flags.DEFINE_boolean('verbose', False,
AttributeError: 'module' object has no attribute 'DEFINE_boolean'



When I use command nova get-vnc-console testVM novnc




+---++
| Type | Url |
+---++
| novnc | 
http://192.168.0.202:6080/vnc_auto.html?token=e1095862-deb9-4cb5-9ec9-44aa0200342e
 |
+---++



but When pasted the url above into my chrome ,I got the following :

Oops! Google Chrome could not connect to 192.168.0.202:6080

Suggestions:

Try reloading the page

Search on Google:when I click the "VNC " tag in dashboard ,I got the folloing :




This webpage is not available
Google Chrome's connection attempt to 192.168.0.202 was rejected. The website 
may be down, or your network may not be properly configured.

Here are some suggestions:

Reload this webpage later.

Check your Internet connection. Restart any router, modem, or other network 
devices you may be using.

Add Google Chrome as a permitted program in your firewall's or antivirus 
software's settings. If it is already a permitted program, try deleting it from 
the list of permitted programs and adding it again.

If you use a proxy server, check your proxy settings or contact your network 
administrator to make sure the proxy server is working. If you don't believe 
you should be using a proxy server, adjust your proxy settings: Go to the 
wrench menu > Settings > Under the Hood > Change Proxy Settings... and make 
sure your configuration is set to "no proxy" or "direct."

Error 102 (net::E