12:32 p.m.
use existing (amazon provided) key to launch instance on ec2
------------------------------------------------------------
Key: JBIDE-7763
URL: https://jira.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7763) use existing (amazon provided) key to launch instance on ec2
[
https://jira.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin.s...
]
Andre Dietisheim updated JBIDE-7763:
------------------------------------
Description:
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
was:
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
use existing (amazon provided) key to launch instance on ec2
------------------------------------------------------------
Key: JBIDE-7763
URL: https://jira.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7763) workflow is weird when it comes up to key workflow
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-7763:
------------------------------------
Summary: workflow is weird when it comes up to key workflow (was: use existing
(amazon provided) key to launch instance on ec2)
workflow is weird when it comes up to key workflow
--------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:08 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7763) workflow is weird when it comes up to key workflow
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-7763:
------------------------------------
Priority: Critical (was: Major)
workflow is weird when it comes up to key workflow
--------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-7763:
------------------------------------
Summary: workflow is weird when it comes up to key management (was: workflow is weird
when it comes up to key workflow)
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-7763:
-----------------------------------------
DeltaCloudClient#listKeys is implemented.
Next step is to adapt the key management UI. It shall list server available keys instead
of the keys that are available on the local filesys.
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-7763:
-----------------------------------------
I revamped the whole manage keys page to deal with keys on the server (list, refresh,
create, delete). What's missing yet is that keys get stored on disk for RSE.
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-7763:
-----------------------------------------
I currently hit what I believe is a bug in the server:
The server does not report the key that was used to create an instance.
I request the following when I create the instance (the key is set: keyname=ad):
http://try.steamcannon.org/deltacloud//api/instances?image_id=ami-7d07ec1...
The server then responds without it (<keyname></keyname>):
<?xml version='1.0' encoding='utf-8' ?>
<instance href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef&...
id='i-82a4b6ef'>
<name>ami-7d07ec14</name>
<owner_id>357159121505</owner_id>
<image href='http://try.steamcannon.org/deltacloud/api/images/ami-7d07ec14'
id='ami-7d07ec14'></image>
<realm href='http://try.steamcannon.org/deltacloud/api/realms/us-east-1a'
id='us-east-1a'></realm>
<state>PENDING</state>
<hardware_profile
href='http://try.steamcannon.org/deltacloud/api/hardware_profiles/m1....
id='m1.small'>
</hardware_profile>
<actions>
<link
href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef/...
method='post' rel='stop' />
</actions>
<launch_time>2010-12-25T14:42:22.000Z</launch_time>
<public_addresses>
</public_addresses>
<private_addresses>
</private_addresses>
<authentication type='key'>
<login>
<keyname></keyname>
</login>
</authentication>
</instance>
I created a bug in the deltacloud jira: https://issues.apache.org/jira/browse/DTACLOUD-11
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-7763:
-----------------------------------------
I implemented a workaround to get around the deltacloud bug described above.
I now add/remove the key to/from the ssh preferences (Network Connections -> SSH2 ->
Private keys)
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim resolved JBIDE-7763.
-------------------------------------
Resolution: Done
committed to TRUNK (CR1)
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Andre Dietisheim edited comment on JBIDE-7763 at 12/29/10 6:05 PM:
-------------------------------------------------------------------
I currently hit what I believe is a bug in the deltacloud fork that runs on
try.steamcannon.org:
The instance I launch has no key pair (that's what the aws console tells me).
The deltacloud server on try.steamcannon.org does not report the key that was used to
create the instance.
1) I request the following when I create the instance (the key is set: keyname=ad):
http://try.steamcannon.org/deltacloud//api/instances?image_id=ami-7d07ec1...
2) The server then responds without it (<keyname></keyname>):
<?xml version='1.0' encoding='utf-8' ?>
<instance href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef&...
id='i-82a4b6ef'>
<name>ami-7d07ec14</name>
<owner_id>357159121505</owner_id>
<image href='http://try.steamcannon.org/deltacloud/api/images/ami-7d07ec14'
id='ami-7d07ec14'></image>
<realm href='http://try.steamcannon.org/deltacloud/api/realms/us-east-1a'
id='us-east-1a'></realm>
<state>PENDING</state>
<hardware_profile
href='http://try.steamcannon.org/deltacloud/api/hardware_profiles/m1....
id='m1.small'>
</hardware_profile>
<actions>
<link
href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef/...
method='post' rel='stop' />
</actions>
<launch_time>2010-12-25T14:42:22.000Z</launch_time>
<public_addresses>
</public_addresses>
<private_addresses>
</private_addresses>
<authentication type='key'>
<login>
<keyname></keyname>
</login>
</authentication>
</instance>
I created a bug in steamcannon: https://issues.jboss.org/browse/STEAM-303
The local deltacloud I run (0.1.2) does not expose this bug
was (Author: adietish):
I currently hit what I believe is a bug in the server:
The server does not report the key that was used to create an instance.
I request the following when I create the instance (the key is set: keyname=ad):
http://try.steamcannon.org/deltacloud//api/instances?image_id=ami-7d07ec1...
The server then responds without it (<keyname></keyname>):
<?xml version='1.0' encoding='utf-8' ?>
<instance href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef&...
id='i-82a4b6ef'>
<name>ami-7d07ec14</name>
<owner_id>357159121505</owner_id>
<image href='http://try.steamcannon.org/deltacloud/api/images/ami-7d07ec14'
id='ami-7d07ec14'></image>
<realm href='http://try.steamcannon.org/deltacloud/api/realms/us-east-1a'
id='us-east-1a'></realm>
<state>PENDING</state>
<hardware_profile
href='http://try.steamcannon.org/deltacloud/api/hardware_profiles/m1....
id='m1.small'>
</hardware_profile>
<actions>
<link
href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef/...
method='post' rel='stop' />
</actions>
<launch_time>2010-12-25T14:42:22.000Z</launch_time>
<public_addresses>
</public_addresses>
<private_addresses>
</private_addresses>
<authentication type='key'>
<login>
<keyname></keyname>
</login>
</authentication>
</instance>
I created a bug in the deltacloud jira: https://issues.apache.org/jira/browse/DTACLOUD-11
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:37 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7763) workflow is weird when it comes up to key management
[
https://issues.jboss.org/browse/JBIDE-7763?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-7763.
-------------------------------
verified on 3.2.0.v20110110-1949-H35-CR1
workflow is weird when it comes up to key management
----------------------------------------------------
Key: JBIDE-7763
URL: https://issues.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud
server
Expected result:
instance could be launched
Everything works fine if I create a new key or use a key I created within the deltacloud
tools.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5569
days inactive
5612
days old
jbosstools-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Andre Dietisheim (JIRA) -
Libor Zoubek (JIRA)