IBM Cloud - Structured Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

bx cs init affects more than current session

Ticket #: CS0003239

Summary: bx cs init affects more than current session

Details: I'm provisioning two clusters simultaneously.
In the first session I initiated a us-south dal13 build, watched it till it got to the master deployment
At that point I switched to a different session to build a London cluster. I ran "bx cs init --host uk-south.containers.bluemix.net"
I switched back to the first session to check progress
Below you see the effect of running bx init in the second session on the first session.
Please accept an enhancement request to alter behaviour such that different sessions in the same user account should not affect each other in this way.
Best Regards
annnnn

annnnn@atunnn-SL1:/mnt/c/Users/annnn$ bx cs workers atunnn-4x16
OK
ID Public IP Private IP Machine Type State Status Version
kube-dal13-swkdjfjksadsdf245d8a2558daff706771d-w1 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503
kube-dal13-swkdjfjksadsdf245d8a2558daff706771d-w2 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503
kube-dal13-swkdjfjksadsdf245d8a2558daff706771d-w3 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503
annnnn@atunnn-SL1:/mnt/c/Users/annnn$ bx cs workers atunnn-4x16
FAILED

The specified cluster could not be found. Run 'bx cs clusters' to list all clusters you have access to. (E0008)
Incident ID: 1cc5263d-1d27-4c07-8a7c-3902beff173a

annnnn@atunnn-SL1:/mnt/c/Users/annnn$ bx cs clusters
OK
Name ID State Created Workers Datacenter Version
atunnn-4x16 94b457cf1b3d448d8855f3532a99df5d deploying 3 seconds ago 3 lon02 1.7.4_1503
annnnn@atunnn-SL1:/mnt/c/Users/annnn$ bx cs workers atunnn-4x16
OK
ID Public IP Private IP Machine Type State Status Version
kube-lon02-pogophoghghghgfhgg8855f3532a99df5d-w1 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503
kube-lon02-pogophoghghghgfhgg8855f3532a99df5d-w2 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503
kube-lon02-pogophoghghghgfhgg8855f3532a99df5d-w3 - - b1c.4x16 provision_pending Waiting for master to be deployed 1.7.4_1503

  • Guest
  • Jan 2 2018
  • Shipped
Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.