Portworx on the Packet.net Hosted Platform
This guide shows you how you can easily deploy Portworx on the packet.net hosting service.
Other supported bare metal cloud providers are
- Scaleway (use this image: https://github.com/scaleway-community/scaleway-docker)
- Digital Ocean
Step 1: Provision Server
When chosing an instance, verify that you meet the minimum requirements
Portworx recommends a minimum cluster size of 3 nodes.
Step 2: Install Docker for the appropriate OS Version
Portworx recommends Docker 1.12 with Device Mapper.
Step 3: Deploy and Attach Block Storage Volume to Packet Server
Follow the instuctions on Packet’s instructions for installing and attaching to block storage.
Your deployment will look something like following:
Step 4: Install and Run the Packet host utilities for block storage
On each host, download and install the Packet block-storage utilities Use packet-block-storage-attach to attach the block storage to your local node.
Step 5: Determine the local multi-path devices
The attached local block storage will automatically be configured for multipath access, using standard Linux dm-multipath.
Use the following command to identify the multipath devices:
NB: In the case where multiple block devices have been configured for services other than Portworx, pay special attention to identifying which block devices (and which corresponding multipath devices) are assocated with each service.
Step 6: Determine the appropriate network interfaces
Run the standard ifconfig utility to determine which network interface corresponds to your public and private IP address. For CentOS7, your likely public interface will be “team0” and private interface will be “team0:0”. Use “team0” as the Portworx management interface, and “team0:0” as the Portworx data interface. For Ubuntu16, your likely public interface will be “bond0” and private interface will be “bond0:0”. Use “bond0” as the Portworx management interface, and “bond0:0” as the Portworx data interface.
Step 7: Launch
Use the docker run command to launch , substituting the appropriate multipath devices and network interfaces, as identified from the previous steps.
Alternatively, you can either run the ‘px_bootstrap’ script from curl, or construct your own config.json file.
From the server node running container, you should see the following status:
You should also be able to monitor cluster from console: