[JBoss JIRA] Created: (JBIDE-7259) Cannot create a connection to the deltacloud server
by Andre Dietisheim (JIRA)
Cannot create a connection to the deltacloud server
---------------------------------------------------
Key: JBIDE-7259
URL: https://jira.jboss.org/browse/JBIDE-7259
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.M2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
I cannot create a connection to a local deltacloud server v0.0.7. The wizard reports that the URL (http://localhost:3001) is not a valid Deltacloud instance. The server throws an error 500:
RuntimeError - Invalid header value: "*; q=.2":
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:19:in `parse'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:13:in `each'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:13:in `parse'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/header.rb:70:in `initialize'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/media_type.rb:49:in `initialize'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/request.rb:16:in `new'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/request.rb:16:in `media_type'
./lib/sinatra/respond_to.rb:103:in `registered'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `instance_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `before_filter!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:461:in `before_filter!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:600:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `instance_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:566:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:411:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:399:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.3/lib/rack/accept/context.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/methodoverride.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/commonlogger.rb:18:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:1005:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:979:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:33:in `log'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/stats.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:76:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:74:in `catch'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:74:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:54:in `process'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/connection.rb:42:in `receive_data'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/backends/base.rb:57:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/server.rb:156:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/controllers/controller.rb:80:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:177:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:177:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/lib/thin/runner.rb:143:in `run!'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.7/bin/thin:6
/usr/bin/thin:19:in `load'
/usr/bin/thin:19
127.0.0.1 - - [05/Oct/2010 16:32:01] "GET /api.xml HTTP/1.1" 500 30 0.1516
If I connect to the same instance with a browser by slightly chaning the requested URL, I can get the API:
http://localhost:3001/api?format=xml
->
<api driver='mock' version='0.1'>
<link href='http://localhost:3001/api/images' rel='images'>
</link>
<link href='http://localhost:3001/api/storage_volumes' rel='storage_volumes'>
</link>
<link href='http://localhost:3001/api/hardware_profiles' rel='hardware_profiles'>
</link>
<link href='http://localhost:3001/api/instance_states' rel='instance_states'>
</link>
<link href='http://localhost:3001/api/realms' rel='realms'>
</link>
<link href='http://localhost:3001/api/instances' rel='instances'>
<feature name='hardware_profiles'></feature>
<feature name='user_name'></feature>
</link>
<link href='http://localhost:3001/api/storage_snapshots' rel='storage_snapshots'>
</link>
</api>
According to the deltacloud guys, a recent API change disabled content negotiation, so requesting .xml does not work any more. The content type has to be indicated in a url parameter (format=). Furthermore the deltacloud server seems no to be able to process a accept-header the tools use: "*; q=.2":
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7512) cannot launch instance
by Andre Dietisheim (JIRA)
cannot launch instance
----------------------
Key: JBIDE-7512
URL: https://jira.jboss.org/browse/JBIDE-7512
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
how to reproduce:
1) pick an image in the cloud viewer
2) select 'launch instance' in the context menu
3) give it a name in the wizard that pops up & hit finish
Result:
No instance is launched, the log shows the following exception:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: org.jboss.tools.deltacloud.ui.views.CVImageElement cannot be cast to org.jboss.tools.deltacloud.ui.views.CVInstanceElement)
at org.eclipse.swt.SWT.error(SWT.java:4083)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Caused by: java.lang.ClassCastException: org.jboss.tools.deltacloud.ui.views.CVImageElement cannot be cast to org.jboss.tools.deltacloud.ui.views.CVInstanceElement
at org.jboss.tools.deltacloud.ui.views.CVInstancesCategoryElement$2.getChildrenWithSameDeltaCloudInstance(CVInstancesCategoryElement.java:160)
at org.jboss.tools.deltacloud.ui.views.CVInstancesCategoryElement$2.restoreSelection(CVInstancesCategoryElement.java:151)
at org.jboss.tools.deltacloud.ui.views.CVInstancesCategoryElement$2.run(CVInstancesCategoryElement.java:123)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 23 more
Expected result:
An instance with the given name is launched
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7496) Cloud View: cannot stop several instances at once
by Andre Dietisheim (JIRA)
Cloud View: cannot stop several instances at once
-------------------------------------------------
Key: JBIDE-7496
URL: https://jira.jboss.org/browse/JBIDE-7496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
how to reproduce:
1) select a connection
2) go to the instances
3) select several running instances (all must be running or the context-menu will not offer STOP)
4) choose STOP from the context menu
5) control the instance states in the properties view
Result:
only the first of the selected instances is stopped
Expected result:
A selection dialog is opened and offers to check the instances that shall be stopped
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7501) Cloud View: cannot reboot several instances at once
by Andre Dietisheim (JIRA)
Cloud View: cannot reboot several instances at once
---------------------------------------------------
Key: JBIDE-7501
URL: https://jira.jboss.org/browse/JBIDE-7501
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
how to reproduce:
1) select a connection
2) go to the instances
3) select several running instances (all must be running or the context-menu will not offer REBOOT)
4) choose REBOOT from the context menu
5) control the instance states in the properties view
Result:
only the first of the selected instances is rebooted
Expected result:
A selection dialog is opened and offers to check the instances that shall be started
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7502) Cloud View: cannot destroy several instances at once
by Andre Dietisheim (JIRA)
Cloud View: cannot destroy several instances at once
----------------------------------------------------
Key: JBIDE-7502
URL: https://jira.jboss.org/browse/JBIDE-7502
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.Beta2
how to reproduce:
1) select a connection
2) go to the instances
3) select several stopped instances (all must be stopped or the context-menu will not offer DESTROY)
4) choose DESTROY from the context menu
5) control the instance states in the properties view
Result:
only the first of the selected instances is destroyed (disappears from the Cloud View)
Expected result:
A selection dialog is opened and offers to check the instances that shall be destroyed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7062) usage report should track eclipse sessions
by Andre Dietisheim (JIRA)
usage report should track eclipse sessions
------------------------------------------
Key: JBIDE-7062
URL: https://jira.jboss.org/browse/JBIDE-7062
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: usage
Affects Versions: 3.2.0.M2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
There are 2 levels of uniqueness:
- session (aka work session in Eclipse) -> reported as "page view" / "unique page view"
- Eclipse instance -> reported as "New Visitor" / "Returning Visitor"
Eclipse instances are trackable by querying the stats for 'Visitor Type' and the value 'New Visitor'/'Returning Visitor'. My plugin currently counts visits and GA recognizes this and reports accordingly.
It would be nice to have a match towards the sessions, too. Unfortunately I'm still not 100% sure how this stuff works. There are cookies for this (utmb, utmc) but no spec that details the values.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months