Bootstrap setup Docker Engine in Swarm

-

docker-machine create -d virtualbox local

@FOR /f "tokens=*" %i IN ('docker-machine env local') DO @%i


docker run swarm create

docker-machine create -d virtualbox --swarm --swarm-master --swarm-discovery

token://b5a6bbbe593a7a888f01183e47e60eb5     swarm-manager

docker-machine create -d virtualbox --swarm --swarm-discovery

token://b5a6bbbe593a7a888f01183e47e60eb5 swarm-node-1

docker-machine create -d virtualbox --swarm --swarm-discovery

token://b5a6bbbe593a7a888f01183e47e60eb5 swarm-node-2

docker-machine create -d virtualbox --swarm --swarm-discovery

token://b5a6bbbe593a7a888f01183e47e60eb5 swarm-node-3

@FOR /f "tokens=*" %i IN ('docker-machine env --swarm swarm-manager') DO @%i

docker-machine ls



docker info



Containers: 5
 Running: 5
 Paused: 0
 Stopped: 0
Images: 4
Server Version: swarm/1.2.5
Role: primary
Strategy: spread
Filters: health, port, containerslots, dependency, affinity, constraint
Nodes: 4
 swarm-manager: 192.168.99.105:2376
  └ ID: VCUD:O4NX:DOFM:BHIG:UQK3:GRV2:OYBF:KBPA:PUM5:L4PZ:O5EV:SH2P
  └ Status: Healthy
  └ Containers: 2 (2 Running, 0 Paused, 0 Stopped)
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: kernelversion=4.4.27-boot2docker, operatingsystem=Boot2Docker 1.12.3 (TCL 7.2); HEAD : 7fc7575 - Thu Oct 27 17:23:17 UTC 2016, provider=virtualbox, storagedriver=aufs
  └ UpdatedAt: 2016-11-08T11:40:39Z
  └ ServerVersion: 1.12.3
 swarm-node-1: 192.168.99.106:2376
  └ ID: GBVX:DDUD:7ADT:DEKW:IUPX:FEJJ:Z22M:MWIA:DBXV:JOSY:VCTW:UKMU
  └ Status: Healthy
  └ Containers: 1 (1 Running, 0 Paused, 0 Stopped)
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: kernelversion=4.4.27-boot2docker, operatingsystem=Boot2Docker 1.12.3 (TCL 7.2); HEAD : 7fc7575 - Thu Oct 27 17:23:17 UTC 2016, provider=virtualbox, storagedriver=aufs
  └ UpdatedAt: 2016-11-08T11:40:14Z
  └ ServerVersion: 1.12.3
 swarm-node-2: 192.168.99.107:2376
  └ ID: TR3A:Y2VW:3XHX:TNMM:CPA7:ZCL2:HNVW:27SE:2FOR:SGBF:ASMA:5GCC
  └ Status: Healthy
  └ Containers: 1 (1 Running, 0 Paused, 0 Stopped)
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: kernelversion=4.4.27-boot2docker, operatingsystem=Boot2Docker 1.12.3 (TCL 7.2); HEAD : 7fc7575 - Thu Oct 27 17:23:17 UTC 2016, provider=virtualbox, storagedriver=aufs
  └ UpdatedAt: 2016-11-08T11:40:12Z
  └ ServerVersion: 1.12.3
 swarm-node-3: 192.168.99.108:2376
  └ ID: TRZW:WOI4:RDZK:ZEA7:GYZY:KS2C:NUX6:3XXW:4FJW:5U54:RNQX:7BIV
  └ Status: Healthy
  └ Containers: 1 (1 Running, 0 Paused, 0 Stopped)
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: kernelversion=4.4.27-boot2docker, operatingsystem=Boot2Docker 1.12.3 (TCL 7.2); HEAD : 7fc7575 - Thu Oct 27 17:23:17 UTC 2016, provider=virtualbox, storagedriver=aufs
  └ UpdatedAt: 2016-11-08T11:40:51Z
  └ ServerVersion: 1.12.3
Plugins:
 Volume:
 Network:
Kernel Version: 4.4.27-boot2docker
Operating System: linux
Architecture: amd64
CPUs: 4
Total Memory: 4.084 GiB
Name: ddddb3a8c0d2
Docker Root Dir:
Debug mode (client): false
Debug mode (server): false

Comments

Post a Comment

Popular posts from this blog

ActiveMQ, easy to use open source message oriented middleware (MOM)

-
ActiveMQ is message oriented middleware (MOM), useful for receiving and processing asynchronous messages (queues or topics). It is easily integrated with Java based applications (and others) via  the JMS API . ActiveQ offers enterprise scale features which may be required when implementing complex distributred systems such as   High availability with failover. Scalability and clustering through a distributed Network of Brokers. Pluggable persistence stores (JDBC, BDB, JDBM, file system). Distributed destinations and XA support. Caching. Connection pooling. Support for cross language clients such as . NET , C++. Support for scripting environments such as Perl, Python, and Ruby. Multiple Transport layers ( TCP , UDP, multicast, NIO, SSL , Zeroconf, JXTA, JGroups). Download at http://activemq.apache.org/
Read more

Basic Send Message to MQ with Java and IBM MQ JMS

-
package my.mq.samples;   import javax.jms.JMSException; import javax.jms.Session; import javax.jms.TextMessage; import com.ibm.mq.jms.MQQueue; import com.ibm.mq.jms.MQQueueConnection; import com.ibm.mq.jms.MQQueueConnectionFactory; import com.ibm.mq.jms.MQQueueSender; import com.ibm.mq.jms.MQQueueSession; import com.ibm.msg.client.wmq.WMQConstants; public class MQSend {     public static void main(String[] args) { try { MQQueueConnectionFactory cf = new MQQueueConnectionFactory(); cf.setHostName("localhost"); cf.setPort(1414);       cf.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, WMQConstants.WMQ_CM_CLIENT); cf.setQueueManager("QM_GRIDSERVER"); cf.setChannel("SYSTEM.ADMIN.SVRCONN");       MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection(); //MQQueueConnection connection = (MQQueueConnection) cf.createQueueConnection("username","password");  
Read more

Automated Service Monitoring with F5, Consul and Python F5 SDK

-
from f5.bigip import ManagementRoot # Connect to BIG-F5 mgmt = ManagementRoot("test.server.com", "testuser", "testpassword") # Get a list of all pools on the BigIP and print their names pools = mgmt.tm.ltm.pools.get_collection() for pool in pools:     print("+++ \t", pool.name)     for member in pool.members_s.get_collection():         print("\t--- \t",  member.name) # Create a HTTP Monitor for an F5 Pool if mgmt.tm.ltm.monitor.https.http.exists(partition='Common', name='F5Automation_HTTP_Monitor'):     print ("HTTP Monitor Already Exists...") else:     mgmt.tm.ltm.monitor.https.http.create(name="F5Automation_HTTP_Monitor", partition="Common") # Load an existing pool and update its description pool_a = mgmt.tm.ltm.pools.pool.load(name='F5Automation', partition='Common') pool_a.description = "F5Automation" pool_a.monitor = "F5Automation_HTTP
Read more