Revisit manual service registerer

[HeartSaVioR]

This issue addresses #780 and #781

Below content is copied from #780

This is a bit complicated because of Ambari import. Ambari provides ://localhost: so that was fairly easy, but not similar as above configuration.

Thought about manual registration more, and I also found what I was missing: configuration file doesn't have default value hence and we can't get the default value anyway.

We need to define required fields for service and let user also input on registering. Since we add resource file for Hadoop / HBase / Hive in topology, we may not need to define required fields for those services, but need to define for others.

Another issue is current implementation of Component. It contains host information as hosts, port, protocol, which can't handle above case. (different protocol and/or different port)

There're two ways of handle this case:

• allow multiple Components for same component (for example, NIMBUS)
  • hosts could be changed to host
• introduce a new entity for storing ComponentHost
  • move hosts, port, protocol to this entity
  • hosts could be changed to host

Storm

• required
  • nimbus.seeds / nimbus.port => Nimbus component
  • ui.host / ui.port => UI component
• optional
  • nimbus.thrift.max_buffer_size
  • storm.thrift.transport
  • storm.principal.tolocal

Kafka

• required
  • zookeeper.connect
  • listeners -> Broker component
• optional
  • security.inter.broker.protocol

Druid

• required
  • druid.zk.service.host
  • druid.selectors.indexing.serviceName
  • druid.discovery.curator.path

[HeartSaVioR]

792

[HeartSaVioR]

792 was merged. Closing.