Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impossible to create a custom stack and remove dev-machine #3883

Closed
slemeur opened this issue Jan 24, 2017 · 0 comments
Closed

Impossible to create a custom stack and remove dev-machine #3883

slemeur opened this issue Jan 24, 2017 · 0 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@slemeur
Copy link
Contributor

slemeur commented Jan 24, 2017

Creating a custom stack from a simple recipe is almost not possible.

The use case is simple:
I want to create a custom stack with a simple recipe
"FROM stevanlm/my_custom_stack"

I ran into different sort of issues which are making the flow very complex:
1- The custom stack was already "preconfigured" with a recipe, I didn't know how to change it
2- I added a second machine, but was still not able to delete the previous "dev-machine"
3- I renamed my new machine by "dev-machine" and I had some mixed values

See the following gif recorded on codenvy.io, but same behaviour on Che.

ae5b7e96-df5f-11e6-9a0c-a448fad2cc0c

See the following issue from Codenvy: codenvy/codenvy#1578

The problem is about the following use case:
As a user, I want to create a new stack and change the recipe used for a machine.

The flow is the following today:

  • I go to “Stack”, click on “Add Stack"
    —> A new stack is created, and with this stack, there is a default dev-machine preconfigured, using the image “codenvy/ubuntu_jdk8"

  • Here, user is quite lost. He can’t change that recipe, unless he changes it in the raw configuration of the stack.

—> We should have the ability to edit the recipe used for one of the machine (just an edit popup, as we do for the name of the stack)

The second problem is a bug.
When you add a second machine with name “toto” and then rename it with the name “dev-machine”, it craps the whole stack recipe.

Che version: 5.0.0 - 5.1.0

@slemeur slemeur added kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. severity/P1 Has a major impact to usage or development of the system. team/plugin and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Jan 24, 2017
@akurinnoy akurinnoy added the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 16, 2017
@akurinnoy akurinnoy removed the status/in-progress This issue has been taken by an engineer and is under active development. label Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants