diff --git a/doc_images/1-welcome.PNG b/doc_images/1-welcome.PNG deleted file mode 100644 index fcc852aed..000000000 Binary files a/doc_images/1-welcome.PNG and /dev/null differ diff --git a/doc_images/2-create-wizard.PNG b/doc_images/2-create-wizard.PNG deleted file mode 100644 index 58c2b4fdd..000000000 Binary files a/doc_images/2-create-wizard.PNG and /dev/null differ diff --git a/doc_images/3-create-summary.PNG b/doc_images/3-create-summary.PNG deleted file mode 100644 index 2a640c5ac..000000000 Binary files a/doc_images/3-create-summary.PNG and /dev/null differ diff --git a/doc_images/4-resources-no-peers.PNG b/doc_images/4-resources-no-peers.PNG deleted file mode 100644 index f1570a189..000000000 Binary files a/doc_images/4-resources-no-peers.PNG and /dev/null differ diff --git a/doc_images/5-after-added-peer.PNG b/doc_images/5-after-added-peer.PNG deleted file mode 100644 index 3d5bface9..000000000 Binary files a/doc_images/5-after-added-peer.PNG and /dev/null differ diff --git a/doc_images/7a-create-channel.PNG b/doc_images/7a-create-channel.PNG deleted file mode 100644 index c8981e637..000000000 Binary files a/doc_images/7a-create-channel.PNG and /dev/null differ diff --git a/doc_images/7b-create-channel.PNG b/doc_images/7b-create-channel.PNG deleted file mode 100644 index 87c71e568..000000000 Binary files a/doc_images/7b-create-channel.PNG and /dev/null differ diff --git a/doc_images/7c-create-channel.PNG b/doc_images/7c-create-channel.PNG deleted file mode 100644 index 0f2766898..000000000 Binary files a/doc_images/7c-create-channel.PNG and /dev/null differ diff --git a/doc_images/7e-create-channel.PNG b/doc_images/7e-create-channel.PNG deleted file mode 100644 index 941123e39..000000000 Binary files a/doc_images/7e-create-channel.PNG and /dev/null differ diff --git a/doc_images/8-created-channel.PNG b/doc_images/8-created-channel.PNG deleted file mode 100644 index 65f07b37f..000000000 Binary files a/doc_images/8-created-channel.PNG and /dev/null differ diff --git a/doc_images/bluemix_ibc1.png b/doc_images/bluemix_ibc1.png index 2d7605389..cf53ba1e6 100644 Binary files a/doc_images/bluemix_ibc1.png and b/doc_images/bluemix_ibc1.png differ diff --git a/doc_images/bluemix_ibc10.png b/doc_images/bluemix_ibc10.png new file mode 100644 index 000000000..cb234c0f4 Binary files /dev/null and b/doc_images/bluemix_ibc10.png differ diff --git a/doc_images/bluemix_ibc11.png b/doc_images/bluemix_ibc11.png new file mode 100644 index 000000000..1b6a6d09b Binary files /dev/null and b/doc_images/bluemix_ibc11.png differ diff --git a/doc_images/bluemix_ibc12.png b/doc_images/bluemix_ibc12.png new file mode 100644 index 000000000..1065bb2f8 Binary files /dev/null and b/doc_images/bluemix_ibc12.png differ diff --git a/doc_images/bluemix_ibc13.png b/doc_images/bluemix_ibc13.png new file mode 100644 index 000000000..da5808e72 Binary files /dev/null and b/doc_images/bluemix_ibc13.png differ diff --git a/doc_images/bluemix_ibc14.png b/doc_images/bluemix_ibc14.png new file mode 100644 index 000000000..3fc808383 Binary files /dev/null and b/doc_images/bluemix_ibc14.png differ diff --git a/doc_images/bluemix_ibc2.png b/doc_images/bluemix_ibc2.png index d34a65c46..80467084d 100644 Binary files a/doc_images/bluemix_ibc2.png and b/doc_images/bluemix_ibc2.png differ diff --git a/doc_images/bluemix_ibc3.png b/doc_images/bluemix_ibc3.png index ef28a66b9..7583c7b61 100644 Binary files a/doc_images/bluemix_ibc3.png and b/doc_images/bluemix_ibc3.png differ diff --git a/doc_images/bluemix_ibc4.png b/doc_images/bluemix_ibc4.png index 112899e6c..c16229742 100644 Binary files a/doc_images/bluemix_ibc4.png and b/doc_images/bluemix_ibc4.png differ diff --git a/doc_images/bluemix_ibc5.png b/doc_images/bluemix_ibc5.png new file mode 100644 index 000000000..5a4226a55 Binary files /dev/null and b/doc_images/bluemix_ibc5.png differ diff --git a/doc_images/bluemix_ibc6.png b/doc_images/bluemix_ibc6.png new file mode 100644 index 000000000..4be36dbea Binary files /dev/null and b/doc_images/bluemix_ibc6.png differ diff --git a/doc_images/bluemix_ibc7.png b/doc_images/bluemix_ibc7.png new file mode 100644 index 000000000..3778fd6d3 Binary files /dev/null and b/doc_images/bluemix_ibc7.png differ diff --git a/doc_images/bluemix_ibc8.png b/doc_images/bluemix_ibc8.png new file mode 100644 index 000000000..72f748de8 Binary files /dev/null and b/doc_images/bluemix_ibc8.png differ diff --git a/doc_images/bluemix_ibc9.png b/doc_images/bluemix_ibc9.png new file mode 100644 index 000000000..f238d2836 Binary files /dev/null and b/doc_images/bluemix_ibc9.png differ diff --git a/docs/use_bluemix_hyperledger.md b/docs/use_bluemix_hyperledger.md index 5f088491e..eb9ea8cc6 100644 --- a/docs/use_bluemix_hyperledger.md +++ b/docs/use_bluemix_hyperledger.md @@ -1,10 +1,8 @@ # Use IBM Cloud Blockchain Service: -### Creating a Blockchain Network in IBM Cloud -1. Don't fret, this is as simple as clicking on a particular button and filling out a text input field or two, or three. - Meh it’s about a dozen. - But that’s not too bad. - The IBM Cloud service will run our peers and orderer, thus forming our blockchain network. +### Creating a Blockchain Network in IBM Cloud (Starter Plan) +1. Don't fret, this is as simple as clicking on a particular button and filling out a text input field or two. + The IBM Cloud service will run our peers and orderer which forms our blockchain network. We also have the ability to join other networks, but let’s focus on creating our own. 1. First [create an IBM ID](https://console.ng.bluemix.net/registration/) if you do not already have one. @@ -17,88 +15,82 @@ ![](/doc_images/bluemix_ibc2.png) -1. You should now be on the Blockchain Platform page where you can find more blockchain related information -1. Click the blue "Service Plan" button +1. Once you selected the blockchain tile you will see the service instance creation screen. This is where you select where the service will be created. Each drop down will allow you to select what Region/Org/Space to create the service. + - You can leave these settings alone if you are new to IBM Cloud or Cloud Foundry. These settings control the Cloud Foundry way of organizing services and applications. If these terms confuse you then leave the default values alone. ![](/doc_images/bluemix_ibc3.png) -1. The service will be created in the currently selected space. This is found on the top toolbar near your email address. Click the space if you want to create the Blockchain service in a different space. This will bring up multiple options for Region/Org/Space. - - All of this is a IBM Cloud concept for organizing services/apps. If these terms confuse you then leave the values alone. +1. Leave the "Service Name" alone or you can choose to rename it to something more meaningful such as "Awesome Marbles" +1. Scroll to the bottom and change the "Selected Plan" to **:lollipop: Starter Membership Plan** or **Enterprise Membership Plan** (these instructions are tailored for starter plan, but the enterprise plan is very similar, you will likely be able to follow along) +1. Click the "Create" button on the bottom right. ![](/doc_images/bluemix_ibc4.png) -1. Leave the "Service Name" alone or you can choose to rename it to something more friendly such as "Awesome Marbles Demo" -1. Leave the "Credential name" field as its default value -1. Leave the "Connected To:" field as "Leave unbound" -1. Scroll to the bottom and change the "Selected Plan" to **:lollipop: Starter Membership Plan (Beta)** or **Enterprise Membership Plan** -1. Click the "Create" button at the bottom right. +- If all goes well you should see a similar screen as the image above. +- Congrats, you have a blockchain network! Click the "Launch" button to enter your blockchain's monitoring UI. +- You are currently eyeballing the "Let's get started!" modal. Dismiss it with the "Got it" button (or read it if you are bored). -![](/doc_images/1-welcome.PNG) +![](/doc_images/bluemix_ibc5.png) - -- If all goes well you should see a similar screen as the image above. Click the "Create Network" button to enter the create wizard. +- Behind that modal is your list of nodes for you network. This is your "Overview" page. -![](/doc_images/2-create-wizard.PNG) +![](/doc_images/bluemix_ibc6.png) -- Now you should see the create network wizard with the words "Let's Get Started". Fill out the whole wizard and I'll meet you on the summary page. If anything confuses you just use the default settings. +- The overview page is listing out your peers, CAs, and orderers. You likely have 1 of each. + - The handy information on this page is the node statuses (hopefully they all say `Running`) and the `View Logs` link which is in the overflow menu at the end of each row (under the `Actions` column). -![](/doc_images/3-create-summary.PNG) - -- Now that we are on the "Review Summary" screen lets look over your choices. When finished click the "Done" button. -- Next you will see an option to create peers or enter the dashboard. Select the "Add Peers" button. - - Make sure you add at least 1 peer. If its too late you can still create the peer later on. - - Click the "Submit" button - -![](/doc_images/4-resources-no-peers.PNG) - -- Congrats, you now have a blockchain network. You are currently eyeballing the list of nodes for you network. This is your "Overview" page. -- You will need nodes called "Peers" to run marbles chaincode. You may have peers already. It depends on if you selected some during the create wizard. If not click the "Add Peer" button and create 1 peer of any size. +- We have one more thing to do for the network setup. We need to make a channel. +- If you are using Starter plan than we already created a channel for you called `defaultchannel`. But I'll run you through the process anyway because its a good thing to know and its non-trivial. + - A channel is used to isolate our blockchain ledger from others on the network. Later we will have the opportunity to invite members of our network to our channel. For now we just want to make a channel for ourself. +- Click the "Channels" link on the left navigation menu. -![](/doc_images/5-after-added-peer.PNG) +![](/doc_images/bluemix_ibc7.png) -- When you see at least one peer listed in the table, we can move on to making a channel. - - Creating a channel is a bit of a process, so bare with me! - - A channel is used to isolate our blockchain ledger from others on the network. (Later we will have the opportunity to invite members of our network to our channel) Members on the same channel will be able to validate each others transactions. For now we just want to make a channel for ourself. -- Click the "Channels" link on the left navigation menu. -- Next click the create "New Channel" button in the top right. You will see a panel similar to the image below. +- Next click the create "Request Channel" button in the top right. You will see a panel similar to the image below. -![](/doc_images/7a-create-channel.PNG) +![](/doc_images/bluemix_ibc8.png) - Give your channel a name and description if you want - Due to the crazy rules it may take a few minuets to pick a good name. Stick to lowercase letters, numbers, dashes, and dots. - Then click "Next" -![](/doc_images/7b-create-channel.PNG) +![](/doc_images/bluemix_ibc9.png) - We need ourself added as an "Operator". So find your email address and check the Operator box next to it. - Operator means we get to vote on changes to this channel. - If we wanted to invite others to the channel, we could add them from the drop down and select their roles. For now lets only have ourself on this channel. - Then click the "Next" button -![](/doc_images/7c-create-channel.PNG) +![](/doc_images/bluemix_ibc10.png) - The update policy decides what it takes to make changes to the channel. In this case how many operators should it take. Since we only have ourself on the channel, the only value that makes sense is 1. Use the dropdown to set this to 1. - Then click the "Submit Request" button -![](/doc_images/7e-create-channel.PNG) +![](/doc_images/bluemix_ibc11.png) - OK. So the request is made, but we still have to sign it and submit it. - In the "Notifications" tab look for a pending request with your channel name on it. - Open the request by clicking the big giant button in the Actions column called "Review Request" - You could review it by expanding each section, but since we made it we know whats inside -- With the notification opened we can now sign the request by clicking "Accept" -- After clicking accept the notification will close -- Next submit the request with the same "Actions" column, but this time click "Submit Request" button -![](/doc_images/8-created-channel.PNG) +![](/doc_images/bluemix_ibc12.png) + +- With the notification opened we can now sign the request by clicking "Approve" + - After clicking "Approve" the notification will close +- Next submit the request with the "Submit Request" button + +![](/doc_images/bluemix_ibc13.png) - Now browse to the "Channels" page in the left navigation menu. It should look similar to the image above. - If all went well you should see the channel name listed after the panel refreshes + +![](/doc_images/bluemix_ibc14.png) + - But we are not quite done... Click the dots in the action column and select the "Join Peers" option -- A menu will appear, check all of your peers and then click the "Add Selected" button +- A menu will appear, check all of your peers and then click the "Join Selected" button - If the stars align the peer will be joined to your channel and everything is done - - You can tell it was successful if the date created and block height (on the channels page) have dates and a number, instead of a '-' - - If you don't see a date, refresh the page or repeat the join + - You can tell it was successful if the date created and block height (on the channels page) have dates and a number, instead of a '-' + - If you don't see a date, refresh the page or repeat the join ### Finish Up Congrats! The network is all setup. If you want more detail on the IBM Blockchain service, available plans, or a detailed overview of the IBM Blockchain Dashboard, jump over [here](https://console.ng.bluemix.net/docs/services/blockchain/index.html?pos=2). If not let’s continue the setup.