[JBoss JIRA] (JBDS-3278) OpenShift v3
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Jeff Cantrill reassigned JBDS-3278:
-----------------------------------
Assignee: Jeff Cantrill (was: Andre Dietisheim)
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Jeff Cantrill
> Fix For: 9.0.0.GA
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image)
> {quote}
> Use Case #1 assumes a TON about what has happened before me.
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3278:
-----------------------------------
Description:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
{quote}
It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
Our Eclipse end-user needs to be able to “browse” for it and select it
git clone it
make changes
git push it back
{quote}
This gives us 3 main use cases (as in mail and chats):
# Import existing OpenShift project (JBDS-3297)
# Push Changes to Existing OpenShift project (JBDS-3298)
# New Project from Template (template should have a default buildconfig, deployconfig and docker image)
{quote}
Use Case #1 assumes a TON about what has happened before me.
- Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
- Assumes end-user is already logged in (there is no auth method at this time)
- Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
{quote}
was:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
{quote}
It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
Our Eclipse end-user needs to be able to “browse” for it and select it
git clone it
make changes
git push it back
{quote}
This gives us 3 main use cases (as in mail and chats):
# Import existing OpenShift project (JBDS-3297)
# Push Changes to Existing OpenShift project (JBDS-3298)
# New Project from Template (template should have a default buildconfig, deployconfig and docker image)
{quote: "Forget everything you know about OpenShift"}
Use Case #1 assumes a TON about what has happened before me.
- Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
- Assumes end-user is already logged in (there is no auth method at this time)
- Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
{quote}
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 9.0.0.GA
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image)
> {quote}
> Use Case #1 assumes a TON about what has happened before me.
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3278:
-----------------------------------
Description:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
{quote}
It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
Our Eclipse end-user needs to be able to “browse” for it and select it
git clone it
make changes
git push it back
{quote}
This gives us 3 main use cases (as in mail and chats):
# Import existing OpenShift project (JBDS-3297)
# Push Changes to Existing OpenShift project (JBDS-3298)
# New Project from Template (template should have a default buildconfig, deployconfig and docker image)
{quote: "Forget everything you know about OpenShift"}
Use Case #1 assumes a TON about what has happened before me.
- Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
- Assumes end-user is already logged in (there is no auth method at this time)
- Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
{quote}
was:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
{quote}
It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
Our Eclipse end-user needs to be able to “browse” for it and select it
git clone it
make changes
git push it back
{quote}
This gives us 3 main use cases (as in mail and chats):
# Import existing OpenShift project (JBDS-3297)
# Push Changes to Existing OpenShift project (JBDS-3298)
# New Project from Template (template should have a default buildconfig, deployconfig and docker image)
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 9.0.0.GA
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image)
> {quote: "Forget everything you know about OpenShift"}
> Use Case #1 assumes a TON about what has happened before me.
> - Assumes that OpenShift Enterprise is installed, configured and running happily at an accessible URL
> - Assumes end-user is already logged in (there is no auth method at this time)
> - Assumes that someone else (not our eclipse end-user) has manually created his/her “project” with an image, a git repo, a deployment config, a build config, defined routes, defined services, etc.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3278:
-----------------------------------
Description:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
{quote}
It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
Our Eclipse end-user needs to be able to “browse” for it and select it
git clone it
make changes
git push it back
{quote}
This gives us 3 main use cases (as in mail and chats):
# Import existing OpenShift project (JBDS-3297)
# Push Changes to Existing OpenShift project (JBDS-3298)
# New Project from Template (template should have a default buildconfig, deployconfig and docker image)
was:
As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 9.0.0.GA
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
> For June @Burr tells us to implement (Mail "Forget everything you know about OpenShift"):
> {quote}
> It could be as simple as…somewhere in OpenShift v3 is the git URL to a source repo….
> Our Eclipse end-user needs to be able to “browse” for it and select it
> git clone it
> make changes
> git push it back
> {quote}
> This gives us 3 main use cases (as in mail and chats):
> # Import existing OpenShift project (JBDS-3297)
> # Push Changes to Existing OpenShift project (JBDS-3298)
> # New Project from Template (template should have a default buildconfig, deployconfig and docker image)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3304) [unit test] versionwatch should run against latest builds, not hardcoded older Betas
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3304?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3304:
-----------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> [unit test] versionwatch should run against latest builds, not hardcoded older Betas
> ------------------------------------------------------------------------------------
>
> Key: JBDS-3304
> URL: https://issues.jboss.org/browse/JBDS-3304
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 8.0.1.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> versionwatch should run against latest builds, not hardcoded older Betas.
> Need a way to pull the latest builds from /staging/ so that instead of testing hardcoded Beta2 builds we use the latest.
> This might have broken as a result of a bug in install.jbds.sh - I thought this used to work:
> {code}
> ++ TMPDIR=/tmp
> /mnt/hudson_workspace/workspace/devstudio.versionwatch_8.0.luna/sources/vwatch/install.jbds.sh: command substitution: line 151: unexpected EOF while looking for matching `"'
> /mnt/hudson_workspace/workspace/devstudio.versionwatch_8.0.luna/sources/vwatch/install.jbds.sh: command substitution: line 152: syntax error: unexpected end of file
> {code}
> Either way, we need a better unit test here to ensure that the versions diffed are NOT just the list of hardcoded ones, but instead include the hardcoded list + at least one more (latest build).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months
[JBoss JIRA] (JBDS-3278) OpenShift v3
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3278?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-3278:
-----------------------------------
These are features/capabilities currently NOT planned for OpenShift v3's Eclipse Tooling:
1) Create SSH Keys
2) Upload SSH Keys
3) Create Domain
4) Add a database, message broker, cache (embeddable cartridge)
5) Show In Web Browser
6) Review Env Vars
7) Edit Env Vars
8) Review Logs
9) Log Streaming
10) SSH in
11) Delete/Destroy
12) Remote Debugging (though that might "just work")
13) Snapshot creation
14) Snapshot restore
15) Port Forwarding
16) Marker Files
17) Node.js
18) PHP
19) Python
20) C++
21) Perl
> OpenShift v3
> ------------
>
> Key: JBDS-3278
> URL: https://issues.jboss.org/browse/JBDS-3278
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Andre Dietisheim
> Fix For: 9.0.0.GA
>
>
> As an OpenShift v3 end-user, I need to be deploy, undeploy, add, remove, view logs, etc. for applications targeting the v3 API.
> The UI for OpenShift Explorer will need to be expanded (or replaced) to handle v3's new terminology and architecture.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 5 months