With the end of the year quickly approaching, it is a great time to look back on the past year, and to look forward in anticipation for what is coming in 2018.
2017 was an interesting year. I saw an explosion in the development of chatbots of various different types. Some were very simple, others used both Watson Conversation and the Watson Discovery service to provide a deeper user experience – with an ability to answer both short tail and long tail questions. I saw a huge uptick in interest in basic Cloud approaches, and a lot of interest in containers and Kubernetes. I expect that both of these trends will continue into 2018.
In 2018 I expect to see the IBM Cloud mature and expand in it’s ability to quickly provide development, test and production computing environments for our customers. I also expect that more people will become interested in hybrid cloud approaches, and will want to understand some best practices for managing these complex environments. I am also excited about some of the excellent cognitive projects that I have seen which could soon be in production for our customers. I also expect that some of our more advanced customers will be looking at how cognitive technologies can be incorporated into their current DevOps processes, and how these processes can be expanded into the cloud.
I hope that your 2017 was a good one, and I hope that you have a happy and safe holiday season.
Just went through an issue with a customer, and it’s a somewhat common issue so I figured that I would do a quick blog post on it.
Recently IBM has decided to rebrand our cloud from what we commonly refer to as Bluemix, and we are now referring to as the IBM Cloud. You may have noticed the changes to the UI, and some new capability (like resource groups!).
Some of these changes have caused some of our customers to “lose” access to some of their data on Bluemix the IBM Cloud (see, even we struggle with the changes in names). These customers claim that they can not see some of the organizations, spaces and services that they used to have. DON’T PANIC!. Your work has not been lost. What has happened is that as IBM has collapsed things to a single IBM Cloud user (when maybe you used to have a SoftLayer user, and a Bluemix user), you now have access to two different accounts from your IBM Cloud web interface.
Fixing the Issue
So just go and look at your profile in the IBM Cloud UI. It is the little person icon in the upper right hand corner of your browser.
Now click on the little symbol under Account, and you will notice that you now have access to two different accounts. Some of your artifacts will be in one account, and others will be in the second account. You can switch context here in the UI so you can see what is in each account. Presto!!! Mystery solved, and now you can go back to being insanely productive working out on the IBM Cloud.
I blog when I have to answer questions that I want to more widely share the answers to. It’s also a good way to remember things before a turkey induced amnesia sets in (it’s a week before U.S. Thanksgiving).
Recently I have seen some questions on being able to get access to the data in an IBM Cloud GitHub project. I had just completed doing a quick internal activity for pulling information out of a GitHub Enterprise repository, so I figured that this would be simple. It was…. and it wasn’t. The IBM Cloud GitHub instance isn’t a GitHub Enterprise deployment, it is a GitLab deployment. The GitLab API is a little different from the GitHub Enterprise API. I managed to find a suitable Python package for using the GitLab API, and if you look at the resulting code, it is pretty simple.
So I have created a simple GitHub project (called IBMCloud_GitLab_CSV) that does a quick CSV export of issues from an IBM Cloud GitHub project. It’s a simple example, written in Python, that you should be able to use and tailor, to fit your specific needs. I use small Python programs like this to pull the open issues from a variety of projects, and then I can share the resulting CSV files with project managers and PowerPoint producers who want to report on these sorts of things.
If you need this type of capability, make sure to read the README file for this project, which instructs you on how to modify the code to point at YOUR IBM Cloud GitHub project, and tells you how to get an access token for yourself (which the program needs, in order to be able to log into your GitHub project).
If you want to improve on this example, or even create some type of generic tool for doing this type of thing, please join the IBMCloud_GitLab_CSV GitHub project and begin contributing to it.
As I have said on earlier blog posts, if I have to answer a question more than once, then it’s probably worthy of a blog post. This week I had one of those situations, and thought that it would be good to share because it highlights a few points at very different levels.
Last week I was answering a survey posted by a Watson Speech-to-Text user, who was complaining about how confusing everything was. I found this a bit surprising, as Speech-to-Text is one of the more simple services for developers to work with. The user claimed that their EasyVSL app was telling them that “Watson wasn’t working”. So I quickly checked the Bluemix status board, and found that nothing indicated a loss of service availability. So I asked some more questions and probed a little deeper.
Watson as an Add-On
I found out that the EasyVSL app has a feature which the user can turn on, which will use the Watson Speech-to-Text service. The user just need to add the service credentials for a valid Watson Speech-to-Text service, and the EasyVSL app will use that Watson service instance to do their speech-to-text processing. Once I saw this, I walked through creating an instance of the Watson Speech-to-Text service for the customer, and showed him how to get his service credentials, which he then supplied to the EasyVSL app. Once this was done, Watson was no longer “broken”.
Up until the past few weeks, I had never seen a product use Watson services in this way – as an add-on to an existing capability, where the CUSTOMER needs to provide the Watson service. In this case, EasyVSL doesn’t worry about paying for Watson services. If their customers see value in them then they use them and pay IBM directly for the services that they use. It is a business/operating model that I am beginning to see now.
Advantages and Disadvantages
This type of model has some positives and negatives associated with it, and I think that it depends on your perspective. As an application provider, it is a positive to be able to let your customers pay for the additional functionality that they want. If they don’t need advanced cognitive capabilities, then why should they pay for them? It also allows you to avoid thinking about how your are going to pass charges along to your customers. If you need to monitor customer usage, track how many times they are using the various Watson API’s, and then figure out some way to pass along the costs associated with them, you will end up spending a fair amount of time and effort developing that monitoring and billing infrastructure (not even considering the adjustments that you will need to make to make your business model work).
From a customer perspective, many of the positives become negatives. While I like to have a choice as a customer, I do not like having to deal with two vendors billing me for a single service. I am also not thrilled with the fact that I need to maintain an instance (or multiple instances) of the Watson services. I am paying money to a vendor so THEY can worry about that stuff. The other downside is that as a customer, it is not always apparent which vendor I need to call when I have a problem. That was the issue that I saw this week – the customer that I had helped had reached out for support from both EasyVSL and IBM – and had not gotten very far with either of them.
Future of Watson as an Add-On
I’m not sure if this pattern will become popular, although my gut tells me that it won’t. Most customers don’t like paying multiple vendors for what they perceive as a single service. However, I do note that cell phones are now largely unsubsidized in the US, with customers buying their own phones, and then paying monthly for services that those phones use. In the past, the phones were “free”, and the cost of the phones was “bundled” into the monthly cell phone rate. So there is precedence for this type of model working.
If you are an app provider, it is critical that you think carefully about your approach to how you use the Watson cognitive services, not only from a technical perspective, but also from a business perspective. The business model that you choose will have an impact on your development, operations, and your customers.
Those of you who read my posts know that I work for IBM, and that I work in the Cloud and Cognitive spaces. Recently I have seen some articles on Multi-Cloud Strategies (like this one from the O’Reilly site), and it puzzles me why so many of the things that I see on this topic seem to miss some of the most basic things. The O’Reilly article simplifies things, and misses some very important points. I don’t blame them, it’s hard to boil down a complex concept into a blog post that can be read in 5 minutes. So after explaining this more than once to someone, I figured it was time to write about it.
Getting Started with Cloud Computing
Cloud computing should be thought of as a tool – a tool to squeeze more computing power from a limited budget. At the highest level it allows a customer to stop buying and maintaining their own sever hardware, and “lease” this capability from a Cloud vendor. Now there are multiple things that you need to account for: security, availability, service availability (what kind of services are available), reliability, cost, etc. Due to some of the current limitations of cloud technologies, not ALL workloads are suitable to be moved to the cloud. There is a lot to understand, and it can be overwhelming.
For this reason, many companies decide to move slowly to the cloud, so they can learn and gain experience as they go. This is a great way to learn about what is important, learn about the limitations and concerns that you should have, and to get some experience with cloud. So they select a single cloud provider, and try a couple of pilot projects, moving some portion of their production computing to the cloud.
This is what I would consider a sane and reasonable approach to starting your journey to the cloud. This approach reduces your risk, and allows you to learn as you go, gaining valuable experience and expertise as your initial projects get deployed. Your team will understand he capabilities of your initial cloud vendor, both positive and negative, and will begin to become more comfortable with the whole cloud paradigm. At this point you are not able to leverage the strengths of various cloud vendors, but you don’t really care because you are in learning mode.
Once these initial pilot projects have been completed, you will then branch out to doing some other projects with your original cloud provider, as well as doing some pilot projects with a second cloud provider. This is the next step on your journey to a true multi-cloud strategy. This second cloud provider will seem quite strange, they may have some different terminology, different billing, and different capabilities. At first your teams will not like them, because they are comfortable with what they already know from your initial cloud provider. Give them time to learn – over time your teams will get a more balanced view of the positives and negatives of the cloud vendors.
At this point you should begin building your own knowledge base of the types of use cases and workloads that work particularly well for each cloud vendor, and you should have some kind of rough order of magnitude way to price workloads that have moved to each cloud vendor. Your team should also have a much better understanding of cloud concepts, and understand the differences in terminology between the cloud vendors.
A True Multi-Cloud Strategy
Once you have branched out to a couple of cloud vendors, branching out and evaluating additional vendors should be easy. Your team will be experienced and will understand some of the key capabilities to look for, the things that are important for your organization. You will be able to intelligently pick and choose between cloud vendors, based on price, capability, reliability, and based on your own experience. You’ll be able to make well informed decisions based on your use case, the workload, and choose the best cloud vendor for that particular job. So let’s look at what the positives and negatives of this approach are.
Time – who wants to wait for two years while your team gets the knowledge that they need? Why not just pick a single cloud vendor and be done with it?
Administration – monitoring and managing one cloud supplier can be a pain – managing 4 or 5 of them can be 4-5 times more painful.
Reduced Risk – your investment portfolio should be well diversified, it reduces the risk you face should one of you investments fail. Your portfolio of cloud technology providers should be diversified for the same reason. It allows you to quickly take advantage of new capabilities and technologies, and gives you FLEXIBILITY. If you remember nothing else from this post – remember this point. It is what all of the other articles that I see miss – and it is the single most important benefit.
Avoiding Vendor Lock In – have a cloud provider that is charging you too much? If you’re familiar with other vendors, moving workloads between cloud providers can be easy (especially if you use container technology).
Best of Breed – giving your business the flexibility to choose a cloud provider that best fits their needs allows you to avoid overpaying for capabilities that might go unused with some cloud providers.
Best Practices – each cloud vendor may be strong in a particular area, but your team can generalize these best practices across ALL of your cloud implementations.
So wrapping things up, I think that a multi-cloud strategy IS important. I strongly believe that the benefits of reduced risk and flexibility far outweigh the costs in terms of time (and patience) and administrative overhead. It also allows your IT teams to focus on your core business, and pushes many of the “bread and butter” IT tasks off onto the cloud provider. This allows you to focus and innovate.
I have been spending the summer working with a number of different Bluemix and Watson customers, and one question seems to come up quite frequently. It has a lot of variations, but it all boils down to this:
“How much of the Bluemix and Watson services am I using, and how can I monitor this?”
This is pretty simple to do, and you can even automate it yourself. So it’s worthy of a quick blog post. First let’s start with the interactive monitoring of your usage.
Checking Bluemix Usage
First you’ll need to log into the Bluemix platform, using your IBM ID. When the main screen comes up, you’ll see account option up in the upper right of your browser. Click on “Manage”, and your options will look like this:
If you then select “Billing and Usage”, and then select “Billing”, you will be taken to a screen that will show the current status of your Bluemix subscription (if you have one). It will show how much you have already consumed, as well as how much of your subscription remains. It should look similar to this:
You can scroll down through this report to see more details. You can use this same method and select “Usage” instead of “Billing”, and you can see your current months usage and to see the specific usage on any of the available Bluemix services. There are other things that you may be interested in as well. Check out the Bluemix Docs on Viewing your Usage for more information.
Automating the Process
You can also see usage (although not billing) information by using the Bluemix CLI (Command Line Interface). The two commands that you will be most interested in are “bx billing account-usage” and “bx billing orgs-usage-summary”. A small GitHub project with a command line tool which will dump your account information (using those commands) is called bmxusagetracking. Go out there and grab the code – and then modify it to suit your own needs. The script is simple – it should take no more than 5 minutes to grab it and understand what it is doing and how it is doing it.
I am also looking at creating a Python version of this in the same project area – since I know that some of you would much rather do this in Python – so you can manipulate the returned data and make it more useful. I invite anyone who wants to contribute to the project and improve it, to do so.
In my role as a Watson and Cloud Adoption Manager, I often talk to customers who are new to the IBM Cloud platform (Bluemix) and the Watson services. Often I will spend a good hour or more talking to customers and answering questions about the best way to get started with the organization of the Bluemix environment, and some of the more operational concerns around cloud and cognitive development. Since I find myself answering these questions over and over, I figured it would be good to get this down in a blog post so I could easily share this information with MORE customers. It also helps me remember all the important things when I do talk on the subject.
Getting Started on Bluemix
Signing up for Bluemix is easy, all you need to do is supply a valid email ID which will be associated with the Bluemix account. This is fine for YOU, but what about your ORGANIZATION? When setting up a Bluemix account for your company or organization, it is best to use a functional ID associated with your company. Just keep in mind that the IBM Cloud will be sending out automated emails to this account (warnings about service usage, services being deprecated, new services available, and other things). So you will want to make sure that you choose an email address that is monitored by someone, so you don’t miss any important notifications.
I KNOW it takes a little longer to set up a functional account within your company, and that it is a pain to go through the paperwork to justify it, but not having your Bluemix account tied to an individual will save you A LOT of time, effort and frustration in the future.
Learning the Cloud Concepts
This is a good spot to pause for a second, and take time to understand some of the basic cloud concepts that will impact how you organize yourself on the IBM Cloud. Looking at this picture may help:
The outermost grey box is my Bluemix Account, and this should be associated with a functional ID. This is the functional ID and email address where you will receive communications from the IBM Cloud team. It is also the account which has access to EVERYTHING underneath it.
Inside of that grey box are three blue boxes. These are the Bluemix Organizations, which represent different functional organizations (or projects) within the larger Bluemix Account. Even though the different organizations reside in the same parent Bluemix Account, the resources within those organizations can be limited to visibility to only resources within that Bluemix Organization.
The green boxes inside of each Bluemix Organization represent Bluemix Spaces. A space can be thought of as an individual development environment, or development area, for the development of a cognitive application.
Finally, at the lowest level, are the various Bluemix Services, indicated with the orange circles. These can be Watson based services (like the Watson Conversation service), infrastructure services (like the OpenWhisk service), or other Bluemix capabilities (like the Weather or Blockchain services). Services essentially “live” within a particular space, and the charges associated with a service are calculated and billed against the Bluemix Account. These charges are broken down by Bluemix Organization, for your own internal billing and tracking purposes.
Getting Organized on the IBM Cloud Platform
We’ll assume that you took my advice, and have a generic corporate ID (like IBMcloud@acme.com) that is your Bluemix account. Now let’s get organized to support the development efforts of your organization on the IBM Cloud platform. I’m also going to assume that you have read the great guide to getting organized on the IBM Cloud Platform. It’s good, and it has more detail than what I cover here. It also doesn’t tell you how YOU should set up YOUR IBM Cloud Platform. I’ll give you a “default” setup that you should use as the basis for your strategy in setting up the IBM Cloud Platform, and I’ll indicate options you have and why you might use those options.
We’ll start with our Bluemix account for our fictional Acme Corporation (for this example, we’re using IBMcloud@acme.com). The first thing that we need to do is to create some Bluemix Organizations for ourselves. Now my fictional company is like a lot of other companies out there, it has some divisions, and these divisions don’t often share responsibilities or development assets. So I will start by giving each of the divisions that are looking at doing cognitive development their own Bluemix Organization.
I do this from the command line, using the Bluemix command line interface (CLI). I go over some of the uses for the Bluemix CLI in Getting Bluemix Information for Support and Automation. We want to create some new Organizations within our account, and we also want to create some new Resource Groups. Some of our projects may be hybrid projects, and may use services support by both models – so we need to have associated areas. In this case, we’ll create spaces for the Tau project, the Epsilon project, and the Phi project.
Here is what our command line looks like:
# Set the Bluemix API endpoint
bluemix api https://api.ng.bluemix.net
# Login to Bluemix, with -u username -p password
bluemix login -u IBMCloudAcct@acme.com -p "mypassword"
# Create new Bluemix Organizations for Delivery, Sales, and Marketing
bluemix iam org-create Acme_Delivery
bluemix iam org-create Acme_Sales
bluemix iam org-create Acme_Marketing
# Print a list of all of the Bluemix Organizations for this Bluemix Account
bluemix iam orgs
The first command sets the API endpoint. The second command gets you logged in. The next three commands create your new organizations, and the last command lists all the Bluemix Organizations for your account. Check out the documentation for Bluemix commands for more details. You will now see a listing of all of your new Bluemix Organizations, along with your default organization. Be sure to provide a unique name for your organizations, and PLEASE establish some kind of naming convention. I used <company_name>_<company_division>, you might want to do this too.
Why set up these separate organizations on the IBM Cloud Platform? For a few reasons:
It helps keep the work organized and segregated. With these in place, and once we get spaces set up, we can limit user access to only certain areas.
It allows us to see usage and billing details by organization. I can see exactly what each organization is using, and how much of my total bill each organization is responsible for.
Also keep in mind that these Bluemix Organizations are just a way to organize your IBM Cloud infrastructure. After reading the guide, you may decide to go with Bluemix Organizations that break up areas based on the roles of your users, or specific projects.
Getting a Subscription
To this point in our setup of the IBM Cloud for the fictional Acme Corporation, we have assumed that you have used a “free”, or “trial”, tier of services. These give you enough resources to figure out what you would like to do on the IBM Cloud, and allowed you to build small demo applications based on the IBM Watson services.
Now since we are talking about doing “real” application development work, we’re going to need more capability than these trial and free versions of the services provide. That means that you will need to spend some amount of money to host these various services and capabilities. Check out this nice overview of the various IBM Cloud Account Types to get an idea of your options. The capabilities and limitations of these options differ, so it is important that you understand them.
For our fictional Acme Corporation, we have decided to go with the popular subscription option. To begin the process of getting a subscription, you will want to follow the directions on how to obtain a subscription on the account types page. Make sure that your subscription is associated with the right Bluemix account (the one with the functional ID, remember that?).
Getting Your Development Environments Right
Now that we have our organizations all set up, and our subscriptions associated with the correct divisions within the fictional Acme Corporation, it’s time to set things up for our development teams. Now I understand that some readers are working for smaller, more nimble organizations. You may be fine with doing things in an ad-hoc manner, and that may actually be the best working model for you. What follows is a broad outline of what larger organizations, seeking a better separation of duties, control of environments, and implementation of a more standard software development lifecycle and DevOps culture will want.
We begin with our Bluemix Account and our Bluemix Organizations. For our purposes here, we will focus on just one of our fictional Acme divisions, the Delivery division. You begin by identifying the projects within the division, and you then begin to create Bluemix Spaces for each project. You should also find out what environments each project will need. Most will need a development environment, a test environment, and a production environment (at a minimum). Some projects will want support for additional environments.
For each project, go out and create the appropriate Bluemix Spaces for the project. Spaces need to have unique names. For the sake of keeping things easily identifiable, unique, and organized, I have followed a naming convention of <Project>_<Environment> (you should probably do the same). So for the Acme Delivery division, we have three projects – called Phoenix, WH, and Dizzi. Each has different services that they use (some are common), and the Dizzi project has no need for a pre-production environment.
So now we use the Bluemix CLI to go and create the spaces that we need (Note: This can also be done interactively from the Bluemix UI – but I know that you are interested in automating this, so I will focus on using the CLI):
# Set the Bluemix API endpoint
bluemix api https://api.ng.bluemix.net
# Login to Bluemix, with -u username -p password -o organization
bluemix login -u IBMCloudAcct@acme.com -p "mypassword" -o Acme_Delivery
# Create new Bluemix Spaces within the Acme_Delivery organization
bluemix iam space-create Phoenix_Dev -o Acme_Delivery
bluemix iam space-create Phoenix_Test -o Acme_Delivery
bluemix iam space-create Phoenix_PreProd -o Acme_Delivery
bluemix iam space-create Phoenix_Prod -o Acme_Delivery
bluemix iam space-create WH_Dev -o Acme_Delivery
bluemix iam space-create WH_Test -o Acme_Delivery
# do the remaining spaces in a similar manner
This results in a Bluemix environment within the Acme_Delivery organization which looks like the diagram below.
You can double-check your results either from the Bluemix CLI (using the “bluemix iam spaces” command), or from the IBM Cloud dashboard. You will notice that there are some small yellow circles within each newly created space. These represent the IBM Cloud services that each project will create within these spaces, in order to implement their project. As a Bluemix administrator, you should not have to do this. The creation of needed services should be left to the individual project teams.
Getting Everyone Else Onboard
So now that you have your Bluemix Organizations, projects and environments (Bluemix Spaces) all set up, you are ready to go. All that you have to do now is get your developers and other stakeholders into the environment. The first step is to get your staff to register for Bluemix and to get their own accounts. I STRONGLY suggest that your force them to register with their company email addresses. It will make things easier for you to administer things as time goes on.
After your team has registered, you can invite them to the correct Bluemix Spaces and Bluemix Organizations. So once again we will use the Bluemix CLI, and send the invitations that we need (Note: This can also be done interactively from the Bluemix UI – but I know that you are interested in automating this, so I will focus on using the CLI):
# Set the Bluemix API endpoint
bluemix api https://api.ng.bluemix.net
# Login to Bluemix, with -u username -p password -o organization
bluemix login -u IBMCloudAcct@acme.com -p "mypassword" -o Acme_Delivery
# Send invitations to the various team members within the Delivery division
# arguments are: USER_NAME ORG_NAME ORG_ROLE SPACE_NAME SPACE_ROLE
bluemix iam account-user-invite email@example.com Acme_Delivery OrgAuditor Phoenix_Dev SpaceDeveloper
bluemix iam account-user-invite firstname.lastname@example.org Acme_Delivery OrgAuditor Phoenix_Dev SpaceDeveloper
bluemix iam account-user-invite email@example.com Acme_Delivery OrgAuditor Phoenix_Test SpaceDeveloper
# do the rest of your users in a similar manner
This gets your users added to the proper organizations and spaces. Some important things to keep in mind when assigning organization roles and space roles to your users.
Give everyone OrgAuditor for their ORG_ROLE. This allows them to see what is going on at the organization level, but doesn’t allow them to change anything. The only exceptions to this are the people who do administration of the organization (your Bluemix Administrator), and handle the billing associated with the organization (often the Bluemix Administrator as well).
Space roles are a bit different.
SpaceManager: This role can invite and manage users, and enable features for a given space. You may want to give this to the development lead for the Development spaces, the test lead for the Test spaces, and your operations leader for the Production spaces.
SpaceDeveloper: This role can create and manage apps and services, and see logs and reports. Give this role to developers in the Development spaces, but you probably don’t want anyone with this role in the Testing and Production spaces. This allows you to maintain the stability of these environments (no code changes).
SpaceAuditor: This role can view logs, reports, and settings for the space. This is used for people who might be interested in the development efforts in a given space – but not requiring access to change anything within the space.
You will probably want to automate this, or provide a self-service capability, so people can easily request access to the environments that they need.
Herding the Cats
At this point we have our Bluemix environments set up, and we have our users added into the Bluemix Organizations and Bluemix Spaces where they need to be, with the access that they require. Our fictional Acme environment looks a little something like this:
Each of our divisions now has the ability to control access to their Bluemix areas, and can effectively isolate their various environments. Each is free to use whatever promotion process and DevOps tooling they prefer, or they can utilize the IBM Cloud Toolchains and the IBM Cloud Continuous Delivery service. Use a DevOps solution which addresses ALL parts of your development process, regardless of where they reside.
There are some important things to consider when thinking about the topic of DevOps in conjunction with the IBM Cloud and the IBM Watson services.
Watson services where you do not provide any training data (Document Conversion, Language Translator, Personality Insights, Tone Analyzer, Text-to-Speech (TTS) and Speech-to-Text (STT) ), can be deployed to additional Bluemix Spaces and do not need to have their data migrated from one environment to the next. Keep in mind that on occasion the versions of the API and underlying services may increment, so you will want to control which API endpoints are used for these services. (Note: If you have customized either Text-to-Speech or Speech-to-Text, then these services will need to be migrated from environment to environment.)
For services like Conversation which support an export/import functionality, it means that you can choose to do your training through the REST API, or interactively through the tooling provided on Bluemix. When you are ready to move an instance from one environment to another, you export from one environment, and then create a new instance in the target environment, and import your data.
For services like Discovery, which do not have an export/import capability, you should resist the temptation to train “by hand”, and instead have a script (or series of scripts) that can be used to train your system. In this way, you can more easily create/recreate an instance of the service.
This should give you enough of an overview, and offer you links to enough information, so that you can begin using the IBM Cloud platform to develop cognitive applications with confidence. Technology changes rapidly, so if you see problems with this basic approach, or have some best practices to share, please reach out to me.
Good Reference Materials
Setting up your Bluemix environment – Not a lot of guidance here, but this documentation page on Bluemix has a lot of the basic information that you will need to understand when setting up a DevOps supported development environment for your cloud and cognitive development.
Bluemix CLI– The reference page for the Bluemix specific CLI. Please use the Bluemix commands and not the Cloud Foundry equivalents, to ensure smooth operation of your Cloud environments.