Skip to content

Conversation

pdhanoya-splunk
Copy link
Contributor

@pdhanoya-splunk pdhanoya-splunk commented Jul 8, 2021

Automation for standalone instance with MC CRD:

  • Updated existing test to work with MC CRD
  • Added utils to get content of config map
  • Introduced workflow to run int test and mc test after merges to feature branch

@pdhanoya-splunk pdhanoya-splunk changed the base branch from develop to CSPL-1044 July 8, 2021 21:53
@smohan-splunk
Copy link
Contributor

For the cases, we deploy Standalone first before MC. Do we also need sanity test to deploy MC first and then standalone?

@pdhanoya-splunk pdhanoya-splunk force-pushed the CSPL-1056 branch 2 times, most recently from 7a3bb24 to 5cc4423 Compare July 9, 2021 22:37
mcConfigMapName := enterprise.GetSplunkMonitoringconsoleConfigMapName(deployment.GetName(), enterprise.SplunkMonitoringConsole)
mcConfigMap, err := GetConfigMap(deployment, ns, mcConfigMapName)
if err != nil {
logf.Log.Error(err, "Failed to get MC Conig Map")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "Failed to get MC Config Map"


// CheckPodNameInString checks for pod name in string
func CheckPodNameInString(podName string, configString string) bool {
logf.Log.Info("Check MC Config String has Pod configured", "MC CM String", configString, "POD String", podName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we elaborate on this log? "MC CM String" is unclear

Copy link
Contributor Author

@pdhanoya-splunk pdhanoya-splunk Jul 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. This however common terminology we use internally but I do understand how this can be confusing.


Context("Deploy Monitoring Console", func() {
It("smoke, monitoring_console: can deploy MC CR", func() {
It("smoke, monitoring_console: can deploy MC CR adn", func() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: adn?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo. Will fix.

5. Verify Monitoring Console Pod has correct peers in Peer List
*/

// Deploy MC and wait for MC to be READY
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Isn't "wait for MC to be READY" part actually done on line 67?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It supposed to be for the section from 62-67 however clearly its not clear I will modify

@smohan-splunk
Copy link
Contributor

For the cases, we deploy Standalone first before MC. Do we also need sanity test to deploy MC first and then standalone?

Covered as part of "smoke, monitoring_console: can deploy MC CR adn"

@smohan-splunk smohan-splunk reopened this Jul 12, 2021
@pdhanoya-splunk pdhanoya-splunk changed the base branch from CSPL-1044 to feature-MC/CRD July 12, 2021 19:57
@pdhanoya-splunk pdhanoya-splunk force-pushed the CSPL-1056 branch 2 times, most recently from 00e0684 to 46ccb20 Compare July 12, 2021 20:08
@smohan-splunk smohan-splunk merged commit f42b373 into feature-MC/CRD Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants