![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
JIRA | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Displaying 290 issues at 03/07/17 01:48 AM. |
Project | Key | Summary | Issue Type | Status | Priority | Resolution | Assignee | Reporter | Creator | Created | Last Viewed | Updated | Resolved | Affects Version/s | Fix Version/s | Component/s | Due Date | Watchers | Images | Original Estimate | Remaining Estimate | Time Spent | Work Ratio | Sub-tasks | Linked Issues | Environment | Description | Security Level | Progress | Σ Progress | Σ Time Spent | Σ Remaining Estimate | Σ Original Estimate | Labels | Approvers | Auto Upgrade | Branch | Business Value | Consumer Prefix | Core Properties | Deployment Duration | Deployment Name | Deployment Payload | Detail | Docker Containers | Docker Images | Epic Color | Epic Link | Epic Name | Epic Status | Epic/Theme | Execution Policy | Flagged | IP | Link | Name | Organizations | Parameters | Parent Link | Port | QA Class | Raised during | Rank | Request Type | Request participants | Runs | SSH Public Key | Satisfaction | Service Name | Sprint | Story Points | Team | Test sessions | Threads | Time to first response | Time to resolution | User Name | Development |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Vn-MD | VNMD-761 | Support SAP NW post install automation using jConnector |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Arivalagan Kaliyaperumal | Arivalagan Kaliyaperumal | 27/06/17 04:48 PM | 03/07/17 01:47 AM | 27/06/17 04:48 PM | 0 | Support SAP NW post install automation using jConnector.
Find the attached guide for List of functions for configuring S4HANA Front End Server and S4HANA 1610. jConnector is already part core package in our source base ( com.virtunomic.sap.jco ) |
0|i07ptj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-759 | CVS import into GIT |
Story | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 25/06/17 07:38 PM | 29/06/17 06:24 AM | 27/06/17 07:24 AM | 31/07/17 | 1 | Import CVS into GIT and check if the CVS is history is preserved. We'd prefer that all history be preserved if possible. | Release Engineering | 0|i07pf3: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-737 | NetApp client - avoid exceptions during deletion |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/06/17 07:50 AM | 21/06/17 01:39 PM | 21/06/17 01:38 PM | 21/06/17 01:38 PM | 30/06/17 | 1 | Avoiding exceptions during deletion | 0|i07nnr: | 1 | NTP Service 1 Tier | CTL Lab Readiness-June | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-736 | A10 client - avoid exceptions during deletion |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/06/17 07:50 AM | 14/06/17 01:32 PM | 14/06/17 01:32 PM | 14/06/17 01:32 PM | 1 | Avoiding exceptions during deletion | 0|i07nnj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-735 | Avoiding exceptions during deletion |
Epic | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/06/17 07:49 AM | 22/06/17 05:48 AM | 21/06/17 01:39 PM | 21/06/17 01:39 PM | 1 | During deprovisioning/tear down, resources should be checked for existence before attempt to delete them is made. | ghx-label-3 | Avoiding exceptions during deletion | To Do | 0|i07nnb: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-734 | Provision A10 Application LB fails with: Error creating server SSL template! |
Task | Done | Medium | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 13/06/17 09:10 AM | 14/06/17 10:30 AM | 14/06/17 10:30 AM | 14/06/17 10:30 AM | 0 | Produced by the following steps (if reproducible every time):
1. Deployed A10 Load Balancer service 2. Deployed ws1 : WebServer 3. Deployed ws2 : WebServer - cancelled running deployment 4. Redeploy ws2 : WebServer -> failed java.lang.RuntimeException: java.io.IOException: java.io.IOException: Error creating server SSL template! at com.virtunomic.model.content.packager.A10Support$2.doRun(A10Support.java:749) at com.virtunomic.model.task.ITaskActivityMonitorExt$ActivityRunnable.run(ITaskActivityMonitorExt.java:53) at com.virtunomic.model.task.ExtActivityMonitor.execute(ExtActivityMonitor.java:375) at com.virtunomic.model.task.DelegatingMonitor.execute(DelegatingMonitor.java:60) at com.virtunomic.model.content.packager.A10Support.doProvisionLB(A10Support.java:753) at com.virtunomic.model.content.packager.A10Support.provisionLB(A10Support.java:309) at com.virtunomic.model.content.packager.UpdatePlanExecutor.doExecuteUpdateOperation(UpdatePlanExecutor.java:793) at com.virtunomic.model.content.packager.UpdatePlanExecutor.access$1(UpdatePlanExecutor.java:399) at com.virtunomic.model.content.packager.UpdatePlanExecutor$3.run(UpdatePlanExecutor.java:392) at com.virtunomic.model.content.packager.UpdateProgressMonitor.executeMonitoredUpdateOperation(UpdateProgressMonitor.java:179) at com.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdateOperation(UpdatePlanExecutor.java:396) at com.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdateOperations(UpdatePlanExecutor.java:320) at com.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdate(UpdatePlanExecutor.java:236) at com.virtunomic.model.content.packager.RunUpdateTask.execute(RunUpdateTask.java:109) at com.virtunomic.model.task.TaskRunner.run(TaskRunner.java:36) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:129) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:133) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:97) at com.virtunomic.model.workflow.internal.WorkflowTaskContext.callWorkflow(WorkflowTaskContext.java:101) at com.virtunomic.model.provisioning.tasks.DeclarativeProvisioningTask.execute(DeclarativeProvisioningTask.java:108) at com.virtunomic.model.task.TaskRunner.run(TaskRunner.java:36) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:129) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:133) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:97) at com.virtunomic.model.workflow.internal.WorkflowTaskContext.callWorkflow(WorkflowTaskContext.java:101) at com.virtunomic.model.deploy.RunDeployWorkflowTask.execute(RunDeployWorkflowTask.java:186) at com.virtunomic.model.task.TaskRunner.run(TaskRunner.java:36) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:129) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.impl.ExtendedNodeInstanceImpl.triggerCompleted(ExtendedNodeInstanceImpl.java:47) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:216) at org.jbpm.workflow.instance.node.StateBasedNodeInstance.triggerCompleted(StateBasedNodeInstance.java:196) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:247) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.signalEvent(WorkItemNodeInstance.java:285) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.signalEvent(WorkflowProcessInstanceImpl.java:342) at org.drools.process.instance.impl.DefaultWorkItemManager.completeWorkItem(DefaultWorkItemManager.java:116) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:136) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:133) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:97) at com.virtunomic.model.workflow.internal.WorkflowTaskContext.callWorkflow(WorkflowTaskContext.java:101) at com.virtunomic.model.deploy.DeployServiceTask.execute(DeployServiceTask.java:98) at com.virtunomic.model.task.TaskRunner.run(TaskRunner.java:36) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:129) at com.virtunomic.model.workflow.internal.CustomTaskHandler.executeWorkItem(CustomTaskHandler.java:101) at org.drools.process.instance.impl.DefaultWorkItemManager.internalExecuteWorkItem(DefaultWorkItemManager.java:70) at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:107) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:279) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerCompleted(NodeInstanceImpl.java:238) at org.jbpm.workflow.instance.node.StartNodeInstance.triggerCompleted(StartNodeInstance.java:49) at org.jbpm.workflow.instance.node.StartNodeInstance.internalTrigger(StartNodeInstance.java:41) at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:126) at org.jbpm.ruleflow.instance.RuleFlowProcessInstance.internalStart(RuleFlowProcessInstance.java:35) at org.jbpm.process.instance.impl.ProcessInstanceImpl.start(ProcessInstanceImpl.java:194) at org.jbpm.workflow.instance.impl.WorkflowProcessInstanceImpl.start(WorkflowProcessInstanceImpl.java:309) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcessInstance(ProcessRuntimeImpl.java:170) at org.jbpm.process.instance.ProcessRuntimeImpl.startProcess(ProcessRuntimeImpl.java:140) at org.drools.common.AbstractWorkingMemory.startProcess(AbstractWorkingMemory.java:1098) at org.drools.impl.StatefulKnowledgeSessionImpl.startProcess(StatefulKnowledgeSessionImpl.java:320) at com.virtunomic.model.workflow.internal.WorkflowImpl.start(WorkflowImpl.java:133) at com.virtunomic.model.workflow.WorkflowJobExecution.execute(WorkflowJobExecution.java:40) at com.virtunomic.service.deploy.Execution.execute(Execution.java:308) at com.virtunomic.service.api.job.AbstractJobProcessor$GetJobPoller.run(AbstractJobProcessor.java:175) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: java.io.IOException: Error creating server SSL template! at com.virtunomic.model.content.packager.A10Support.createVirtualServer(A10Support.java:798) at com.virtunomic.model.content.packager.A10Support.access$5(A10Support.java:756) at com.virtunomic.model.content.packager.A10Support$2.doRun(A10Support.java:744) ... 213 more Caused by: java.io.IOException: Error creating server SSL template! at com.virtunomic.a10.client.A10Client.handleException(A10Client.java:3221) at com.virtunomic.a10.client.A10Client.createServerSslTemplate(A10Client.java:788) at com.virtunomic.model.content.packager.A10Support.createVirtualServer(A10Support.java:789) ... 215 more Caused by: java.io.IOException: Request unsuccessfull! HTTP code returned '400', reason 'Bad Request' Code: 1023459339; Message: Failed to handle object "server-ssl". Object already exists; Location: server-ssl; at com.virtunomic.a10.client.A10Client.handleError(A10Client.java:3226) at com.virtunomic.a10.client.A10Client.validateResponse(A10Client.java:3151) at com.virtunomic.a10.client.A10Client.createServerSslTemplate(A10Client.java:784) ... 216 more |
0|i07nfz: | 1 | NTP Service 1 Tier | CTL Lab Readiness-June | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-733 | MAC address verify should provide more actionable information |
Story | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 12/06/17 03:17 PM | 24/06/17 05:22 AM | 14/06/17 10:34 AM | Update Plan Generation | 30/06/17 | 1 | The interface number and IP address should be provided so the recipient of the message understands the context.
The current message looks like: ava.io.IOException: Expected MAC address 00:50:56:86:7d:c3 not found! at com.virtunomic.model.content.packager.MacAddressVerifier.handleException(MacAddressVerifier.java:325) at com.virtunomic.model.content.packager.MacAddressVerifier.verifyMacAddressesUnordered(MacAddressVerifier.java:110) at com.virtunomic.model.content.packager.MacAddressVerifier.verifyMacAddresses(MacAddressVerifier.java:89) |
0|i07ncn: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-720 | VNMD-698 ZooKeeper Agent build |
Sub-task | Done | Medium | Done | Unassigned | Michal Siemaszko | Michal Siemaszko | 24/05/17 06:22 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 0 | 0|i07l07: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-719 | VNMD-698 ZK CLI product build |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 23/05/17 12:04 PM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 0 | 0|i07ksv: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-718 | VNMD-698 DSC product build |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 23/05/17 12:04 PM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 0 | 0|i07ksn: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-713 | MacAddressVerifier should support connection retries when reading guestOS NIC info |
Story | Done | Medium | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 19/05/17 09:01 AM | 29/05/17 11:47 AM | 29/05/17 11:42 AM | 29/05/17 11:42 AM | 26/05/17 | 0 | com.virtunomic.model.content.packager.MacAddressVerifier.readRemoteNicConfiguration(String, int, String, String)
It is possible ssh connection is refused and but is working after exception bellow is thrown: Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at net.schmizz.sshj.SocketClient.connect(SocketClient.java:126) at com.virtunomic.model.content.packager.MacAddressVerifier.readRemoteNicConfiguration(MacAddressVerifier.java:180) |
0|i07i27: | 1 | NTP Service 1 Tier | CTL Lab Readiness-May | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-708 | VNMD-693 POC of automatically generating separate local p2 repositories - RCP only, RAP only |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/05/17 07:20 AM | 11/05/17 11:43 AM | 11/05/17 11:43 AM | 0 | 0|i074kf: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-707 | VNMD-698 Determine available support / plugins available for generating delta repository in Tycho or Maven only and invoke via custom Mojo |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/05/17 07:16 AM | 11/05/17 07:16 AM | 11/05/17 07:16 AM | 0 | 0|i074in: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-704 | VNMD-698 POC of Virtunomic RAP product build |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 09/05/17 12:34 PM | 09/05/17 12:35 PM | 09/05/17 12:35 PM | 0 | Proof of concept of Virtunomic RAP product build to determine what other issues might need to be resolved, based on reduced number of dependencies.
+Features+: * com.virtunomic.core-feature * com.virtunomic.apache.esb-feature * com.virtunomic.eclipse.modeling.runtime.rap-feature * com.virtunomic.rap.product +Plugins+: * com.virtunomic.log * com.virtunomic.common * com.virtunomic.config * com.virtunomic.apache.curator +Fragments+: * com.virtunomic.log.appender.lilith * com.virtunomic.log.appender.logstash +Products+: * com.virtunomic.rap.releng/product/dsc/virtunomic-rap.product |
0|i06zrj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-702 | VNMD-698 Identify and configure features, products, target files |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:18 AM | 23/05/17 12:03 PM | 23/05/17 12:03 PM | 23/05/17 12:03 PM | 31/05/17 | 0 | 0|i06ct3: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-701 | VNMD-698 Determine available support / plugins available for configuring and building different products |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:17 AM | 23/05/17 12:03 PM | 23/05/17 12:03 PM | 23/05/17 12:03 PM | 31/05/17 | 0 | 0|i06csn: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-700 | VNMD-698 Determine available support / plugins available for configuring incremental build in Tycho or Maven only and invoke via custom Mojo |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:16 AM | 11/05/17 07:14 AM | 11/05/17 07:14 AM | 0 | 0|i06cs7: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-699 | VNMD-698 POC of generating POMs for each bundle so Tycho "regular" (instead of POM-less) can be used |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:14 AM | 06/05/17 09:14 AM | 06/05/17 09:14 AM | 0 | 0|i06crj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-698 | Full build / incremental build / product-specific build |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:14 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 26/05/17 10:28 AM | 0 | VNMD-699, VNMD-700, VNMD-701, VNMD-702, VNMD-704, VNMD-707, VNMD-718, VNMD-719, VNMD-720 | (...) Need to have control over updating bundle and feature version identitiers incrementally - so they are versioned individually not as the whole product. This way we can generate a update patches representing a delta against an existing installation base. Currently, this is controlled via using map files with PDE builder and changes are released to map files using Releng Tool, which is not available in Tycho builder. (...)
(...) Tycho based CI build has to be able to produce multiple products, features, which means we should not be required to recompile the whole source base again in order to build different product, features. (...) (...) We need to compile into the same result in IDE and on CI builder (...) |
Migrate CI builder to Tycho | 0|i06crb: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-697 | VNMD-695 Custom Maven plugin for updating bundle qualifier based on map file tag |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:10 AM | 23/05/17 03:03 PM | 23/05/17 03:04 PM | 23/05/17 11:58 AM | 31/05/17 | 0 | Implemented as specialized Mojo / custom Maven plugin - recursively reads in bundles' (features', plugins', fragments') metadata which it finds in sub-folders of base directory from where it's invoked, parses specified map file, and updates bundles' qualifiers to match those defined in map file. | 0|i06cq7: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-696 | VNMD-695 POC of updating bundle qualifier based on map file tag |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:09 AM | 06/05/17 09:09 AM | 06/05/17 09:09 AM | 0 | 0|i06cpr: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-695 | Updating plugin and feature qualifiers |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:07 AM | 23/05/17 03:03 PM | 23/05/17 11:58 AM | 23/05/17 11:58 AM | 0 | VNMD-696, VNMD-697 | (...) Need to have control over updating bundle and feature version identitiers incrementally - so they are versioned individually not as the whole product. (...) | Migrate CI builder to Tycho | 0|i06cpb: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-694 | VNMD-693 POC of ways Tycho can resolve dependencies |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:05 AM | 06/05/17 09:06 AM | 06/05/17 09:06 AM | 0 | 0|i06con: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-693 | Dependency resolution in Tycho |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:05 AM | 26/05/17 10:29 AM | 26/05/17 10:29 AM | 26/05/17 10:29 AM | 0 | VNMD-694, VNMD-708 | (...) Need to ensure deterministic and static dependency resolution, avoid bringing new dependency versions from public repos. Dependency repository should be local (FS) so it is easy to manage for different branches without dealing running a server on a host (...) | Migrate CI builder to Tycho | 0|i06co7: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-692 | VNMD-687 Custom Maven plugin for checking out bundles defined in map file into Tycho-compatible directory layout |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 09:02 AM | 26/05/17 10:29 AM | 23/05/17 03:04 PM | 23/05/17 11:58 AM | 31/05/17 | 0 | Implemented as specialized Mojo / custom Maven plugin - parses specified map file and invokes Maven SCM plugin to check out specific modules, placing them in Tycho-compatible folder structure. | 0|i06cnb: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-691 | VNMD-687 POC of checking out bundles defined in map file into (created on the fly) Tycho-compatible directory layout |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:59 AM | 06/05/17 09:00 AM | 06/05/17 09:00 AM | 0 | 0|i06cmn: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-690 | VNMD-687 Determine how to adopt flat-folder structure to work with Maven SCM plugin |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:58 AM | 06/05/17 09:00 AM | 06/05/17 09:00 AM | 0 | How to check out from CVS where plug-ins are not hierarchical into Tycho-compatible hierarchical structure locally | 0|i06clz: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-689 | VNMD-687 Parsing map file and checking out bundles defined in it |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:58 AM | 06/05/17 09:00 AM | 06/05/17 09:00 AM | 0 | 0|i06clr: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-688 | VNMD-687 POC of using Maven SCM plugin with CVS provider to check out source from CVS repository |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:57 AM | 06/05/17 09:00 AM | 06/05/17 09:00 AM | 0 | 0|i06clj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-687 | Checkout from CVS via Maven |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:56 AM | 23/05/17 03:03 PM | 23/05/17 11:59 AM | 23/05/17 11:59 AM | 0 | VNMD-688, VNMD-689, VNMD-690, VNMD-691, VNMD-692 | (...) Initially, try if Tycho builder is working with CVS so we can solve problem of using Git separately (...) | Migrate CI builder to Tycho | 0|i06ckv: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-686 | VNMD-684 POC of how Project Set Editor can be configured to create such directory layout |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:54 AM | 06/05/17 08:55 AM | 06/05/17 08:55 AM | 0 | 0|i06chr: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-685 | VNMD-684 POC of expected/compatible with Tycho directory layout |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:53 AM | 06/05/17 08:54 AM | 06/05/17 08:54 AM | 0 | 0|i06chj: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-684 | Tycho-compatible directory layout |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/05/17 08:53 AM | 06/05/17 08:55 AM | 06/05/17 08:55 AM | 0 | VNMD-685, VNMD-686 | Migrate CI builder to Tycho | 0|i06ch3: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-682 | ZooKeeper Agent - add support for RabbitMQ server control and status checking |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 04/05/17 07:01 AM | 04/05/17 11:01 AM | 04/05/17 11:01 AM | 2 | ESB upgrade | 0|i05s13: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-662 | License tracking for each jar/library VMD uses |
Story | Selected for Development | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 17/04/17 06:50 AM | 29/06/17 06:24 AM | 27/06/17 06:54 AM | Releng | 30/06/17 | 0 | VNMD-661 | The license for each jara/libarary needs to be obtained and tracked. We need the following kind of information:
# Jar/Library (Maven name and version) # Author # License (e.g. Apache 2.0) Hopefully there is some way we can automate this by using Maven or some related tools. In the end we want this information to be put into a file or DB so we can track and detect when we: * Add more referenced jars/libraries * Consume something with a License we are not familiar with |
Intellectual Property Management | 0|i04sgn: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-661 | Remove redundant Jar/Library across OSGI bundles |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 17/04/17 06:42 AM | 03/07/17 01:46 AM | 13/06/17 08:46 AM | Releng | 30/06/17 | 0 | VNMD-660, VNMD-662 | Many jars/libraries are referenced across clients and components VMD uses, resulting in the same jars/libraries being included in multiple OSGI bundles. This makes the distribution large and requires extra memory.
To the extent possible (e.g. due to version constraints etc.) eliminate these redundancies by using the Maven and the Tyco builder. |
Release Engineering | 0|i04sgf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-660 | Migrate CI builder to Tycho |
Epic | In Progress | Medium | Unresolved | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 14/04/17 02:30 PM | 24/06/17 05:22 AM | 16/06/17 08:42 AM | 31/05/17 | 1 | VNMD-659, VNMD-661 | Migration of the current PDE builder to maven based Tycho builder
Initially, try if Tycho builder is working with CVS so we can solve problem of using Git separately. When doing any tests with Git, we need to use Vnomic Bitbucker account, no public repos Tycho based CI build has to be able to produce multiple products, features, which means we should not be required to recompile the whole source base again in order to build different product, features. Need to ensure deterministic and static dependency resolution, avoid bringing new dependency versions from public repos. Dependency repository should be local (FS) so it is easy to manage for different branches without dealing running a server on a host Need to have control over updating bundle and feature version identitiers incrementally - so they are versioned individually not as the whole product. This way we can generate a update patches representing a delta against an existing installation base. Currently, this is controlled via using map files with PDE builder and changes are released to map files using Releng Tool, which is not available in Tycho builder. We need to compile into the same result in IDE and on CI builder |
ghx-label-11 | Migrate CI builder to Tycho | To Do | 0|i04sg7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-627 | Spring Security optional switching between AD & DAO and DAO only providers |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/03/17 07:50 AM | 24/03/17 08:54 AM | 23/03/17 04:46 PM | 14/04/17 | 2 | Introduce Spring environment profiles to allow switching between AD + DAO (UserDetailsService) provider profile and DAO only provider profile.
This will allow to preserve the built-in to Spring Security mechanism of specifying multiple providers and fallback if authentication fails via provider defined earlier in the list. |
Security | 0|i03grb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-614 | NPE cause by SshjSshClient.FileTransferListener |
Task | Done | High | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 15/03/17 11:44 AM | 17/03/17 01:11 PM | 17/03/17 01:06 PM | 1 | com.virtunomic.model.support.SshjSshClient.FileTransferListener is empty implementation of the listener interface, causes NPE
java.lang.NullPointerException at net.schmizz.sshj.xfer.scp.SCPUploadClient.process(SCPUploadClient.java:78) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPUploadClient.sendDirectory(SCPUploadClient.java:88) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPUploadClient.process(SCPUploadClient.java:76) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPUploadClient.startCopy(SCPUploadClient.java:70) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPUploadClient.copy(SCPUploadClient.java:50) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPUploadClient.copy(SCPUploadClient.java:43) [com.virtunomic.sshj:1.0.0.qualifier] at net.schmizz.sshj.xfer.scp.SCPFileTransfer.upload(SCPFileTransfer.java:73) [com.virtunomic.sshj:1.0.0.qualifier] at com.virtunomic.model.support.SshjSshClient.copyLocalToRemote(SshjSshClient.java:368) [com.virtunomic.model.vml:1.0.0.qualifier] at com.virtunomic.model.state.SshOperatingSystemAccess$4.call(SshOperatingSystemAccess.java:385) [com.virtunomic.model.vml:1.0.0.qualifier] at com.virtunomic.model.state.SshOperatingSystemAccess$4.call(SshOperatingSystemAccess.java:1) [com.virtunomic.model.vml:1.0.0.qualifier] at com.virtunomic.model.runtime.util.Retryer.execute(Retryer.java:22) [com.virtunomic.model.vml:1.0.0.qualifier] at com.virtunomic.model.state.SshOperatingSystemAccess.copyLocalToTarget(SshOperatingSystemAccess.java:395) [com.virtunomic.model.vml:1.0.0.qualifier] at com.virtunomic.model.support.backing.LinuxOnlineDeployedDiskProvider.checkAgent(LinuxOnlineDeployedDiskProvider.java:486) [com.virtunomic.model.vml:1.0.0.qualifier] |
0|i03br3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-605 | VNMD-381 Apache Aries contributions / patches - describe use cases, prepare code, share with Apache Aries project/community |
Sub-task | Backlog | Low | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:52 AM | 12/03/17 11:01 AM | 0 | Prepare short summaries / descriptions of use cases for each (e.g. why we had to patch) and take care of any code preparation necessary for:
* Blueprint Spring Security integration / Blueprint container based Delegating Filter Proxy * Blueprint Webosgi "patch" * Blueprint Spring "patch" |
0|i03az3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-604 | VNMD-381 Clean up 'com.virtunomic.esb.tests' bundle |
Sub-task | Backlog | Low | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:51 AM | 12/03/17 11:01 AM | 0 | 0|i03ayv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-603 | VNMD-381 Cleanup old usage of `com.virtunomic.service.api.springdm.SpringDMUtil` |
Sub-task | Backlog | Low | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:49 AM | 12/03/17 11:00 AM | 0 | Change all calls to 'com.virtunomic.service.api.springdm.SpringDMUtil' to use 'com.virtunomic.service.api.osgi.OSGiServiceRegistryUtil', remove 'SpringDMUtil'; rewrite all usages of `com.virtunomic.service.api.springdm.SpringDMUtil.getLocalServiceReference(Class<T>)` to pass bundle context; | 0|i03ayn: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-602 | VNMD-381 Offline test |
Sub-task | Done | Low | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:47 AM | 21/04/17 03:31 PM | 21/04/17 03:31 PM | 0 | VNMD-572 | Test and debug if necessary to ensure all schemas for all namespaces can be picked up from classpath instead of being fetched from web on each parsing of blueprint / spring XMLs. | 0|i03ayf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-601 | VNMD-381 Report APIC issue to Cisco |
Sub-task | Backlog | Low | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:45 AM | 17/06/17 09:34 AM | 30/06/17 | 0 | We encountered issue with APIC API, for which we implemented a workaround, however should really be resolved on Cisco's side.
Cisco's APIC code does not conform to http://tools.ietf.org/html/rfc6265#section-4.1.1 RFC - i.e. cookie values may be quoted if they contain special characters (and token value returned from APIC contain such characters). APIC code however does not conform to this RFC, it does not check for leading/trailing quotes and strip them, as it should, but treats entire string as actual cookie value. |
0|i03ay7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-600 | VNMD-381 Camel RabbitMQ component custom types serialization optimization |
Sub-task | Backlog | Low | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/03/17 10:43 AM | 12/03/17 11:00 AM | 0 | 'com.virtunomic.camel-rabbitmq.fragment' bundle, used to allow for custom types serialization in Camel RabbitmQ plugin, currently is using "dynamic imports" (i.e. "DynamicImport-Package" header).
Check whether these can be replaced with "regular" imports (i.e. "Import-Package" header). |
0|i03axz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-589 | Install updated certificates on relevant endpoints |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 09/03/17 11:03 AM | 17/06/17 09:35 AM | 30/06/17 | 0 | Client security | 0|i03ahj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-577 | Support MS Active directory authentication |
Story | Done | Medium | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 27/02/17 07:17 AM | 16/03/17 08:48 AM | 16/03/17 08:48 AM | 31/03/17 | 1 | - Leverage Spring Security support for integration and define mapping
to Vnomic principals - Support optional usage of this authentication type allowing to use the basic internal DB based authentication |
Security | 0|i0001a:i60004 | NTP Service 1 Tier | CTL Lab Readiness | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-576 | Investigate sending VMD events to Icinga |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 26/02/17 11:25 AM | 05/04/17 02:33 PM | 05/04/17 02:33 PM | 31/03/17 | 2 | Determine the most efficient and information preserving way to send events received on the ESB to Icinga. Is there something better than SNMP traps?
It's probably important to understand how Icinga receives events from other sources. |
VMD Monitoring | 0|i0001a:i60000001cx | NTP Service 1 Tier | CTL Lab Readiness-April | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-575 | Emit syslog events for VMD lifecycle |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 26/02/17 10:57 AM | 19/06/17 08:19 AM | 23/03/17 12:57 PM | 23/03/17 12:57 PM | 31/03/17 | 0 | VMD life-cycle and status events published to the ESB should be emitted to the GrayLog instance on the Monitoring Server.
The Camel syslog support can be used for this. Provide a method to set the syslog server information in the core.properties file. |
VMD Monitoring | 0|i0001a:i60001zzzzzzr | NTP Service 1 Tier | CTL Lab Readiness | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-572 | Ensure offline mode works fine with namespace handlers |
Task | Done | Low | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 22/02/17 09:22 AM | 21/04/17 03:31 PM | 21/04/17 03:31 PM | 0 | VNMD-602 | ESB upgrade | 0|i0001a:i60001zzzzzzi | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-566 | Create SNMP4J Client |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 17/02/17 02:58 PM | 13/06/17 08:55 AM | 30/06/17 | 0 | Create client OSGI bundle.
Implement unit test whch generates a trap. At the moment we ONLY need to send traps, NOT act like an agent support gets/sets on a MIB. |
SNMP Support | 0|i0001a:i60000001cv | NTP Service 1 Tier | CTL Lab Readiness-April, CTL Lab Readiness-May, CTL Lab Readiness-June | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-561 | SshJ library issues/upgrade |
Story | Done | Highest | Done | Michal Siemaszko | Derek Palma | Derek Palma | 12/02/17 01:13 PM | 13/02/17 12:34 PM | 13/02/17 12:34 PM | 15/02/17 | 2 | We have been getting the following error entries in our log for a long time
[11/09/30 15:20:30][ERROR][net.schmizz.sshj.transport.TransportImpl-570] Dying because - net.schmizz.sshj.connection.ConnectionException: [PROTOCOL_ERROR] Received response to channel request when none was requested [11/09/30 15:20:30][ERROR][net.schmizz.concurrent.Promise-171] <<chan#7 / chanreq for exec>> woke to: net.schmizz.sshj.connection.ConnectionException: [PROTOCOL_ERROR] Received response to channel request when none was requested I (Radek) have found there was a known “Race condition” issue in this library https://github.com/hierynomus/sshj/issues/35 Also we have observed strange issues In our QA executions - java.net.SocketException: Socket closed when writing to socket during ssh command The tasks is to look at available Sshj releases asap and evaluate if we can integrate a newer version into our target easily and execute our test cases. |
Vnomic Meta Director | 0|i034cv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-551 | vSphere client should validate server certificate |
Story | blocked | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 06/02/17 07:32 AM | 27/06/17 06:46 AM | 27/06/17 06:46 AM | 30/06/17 | 3 | Client security | 0|i0001a:i60001v | NTP Service 1 Tier | CTL Lab Readiness, CTL Lab Readiness-April, CTL Lab Readiness-May, CTL Lab Readiness-June | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-550 | NetApp CDOT client should validate server certificate |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/02/17 07:32 AM | 17/04/17 12:21 PM | 17/04/17 12:21 PM | 07/04/17 | 1 | Client security | 0|i0001a:i60001r | NTP Service 1 Tier | CTL Lab Readiness, CTL Lab Readiness-April | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-549 | UCS Manager client should validate server certificate |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/02/17 07:32 AM | 12/04/17 12:15 PM | 12/04/17 12:03 PM | 07/04/17 | 1 | Client security | 0|i0001a:i60001i | NTP Service 1 Tier | CTL Lab Readiness, CTL Lab Readiness-April | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-548 | APIC client should validate server certificate |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/02/17 07:31 AM | 12/04/17 12:15 PM | 12/04/17 12:02 PM | 07/04/17 | 1 | Client security | 0|i0001a:i60001 | NTP Service 1 Tier | CTL Lab Readiness, CTL Lab Readiness-April | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-547 | Clients should validate server endpoint certificates |
Epic | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 05/02/17 09:10 PM | 18/04/17 01:38 PM | 31/03/17 | 3 | VNMD-481, VNMD-500 | Clients like APIC, vCenter, NetApp, UCSM should check and verify the cert provided by the endpoint. The default (production) client behavior should be to check and fail if a trusted cert is not provided (for development we can allow this to be skipped). | ghx-label-4 | Client security | To Do | 0|i03233: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-542 | Prototype adding deployment report contents to service request spreadsheet |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 30/01/17 10:53 AM | 06/02/17 11:48 AM | 06/02/17 11:48 AM | 28/02/17 | 0 | Determine how the service request spreadsheet be updated with deployment report contents. The idea is to update the service request spreadsheet preserving any data the user may have included versus creating a completely new spreadsheet. | Service Requests using Excel Spreadsheets | 0|i030xr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-541 | Apache POI prototype |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 30/01/17 10:37 AM | 06/02/17 11:53 AM | 02/02/17 02:24 PM | 0 | Create a bundle for Apache POI named com.virtunomic.apache.poi and write unit tests to read the service request configuration from the attached sample file. | Service Requests using Excel Spreadsheets | 0|i030wv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-540 | Support Service Requests using Excel Spreadsheets |
Epic | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 30/01/17 10:27 AM | 17/06/17 10:30 AM | 0 | Allow users to specify Service Requests parameters by uploading an Excel spreadsheet instead of JSON.
Server Request results should be added to the input spreadsheet. |
ghx-label-7 | Service Requests using Excel Spreadsheets | To Do | 0|i030wf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-464 | Reporting should include "special function" attribute of IP address binding |
Task | Done | Medium | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 18/10/16 06:52 AM | 18/10/16 08:32 AM | 18/10/16 08:32 AM | Reporting | 0 | This data is available via com.virtunomic.model.deploy.AddressBinding.getSpecialFunction() | 0|i018pj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-436 | VNMD-381 Camel - RabbitMQ integration into Vnomic application - Phase 3 |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 29/08/16 09:56 AM | 07/03/17 07:27 AM | 07/03/17 07:27 AM | 23/09/16 | 2 | Integrate Camel - RabbitMQ solution into Vnomic App. Third phase is to add Camel RabbitMQ configuration, update existing ActiveMQ configuration and resolve any issues that might arise when starting and running Vnomic app. | 0|i015dz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-435 | Ability to consume landscapes' connectivity data for use in reporting |
Story | Backlog | Medium | Unresolved | Radek Dvorak | Michal Siemaszko | Michal Siemaszko | 25/08/16 12:26 PM | 25/08/16 12:27 PM | 1 | VNMD-433 | Need ability to consume landscapes' connectivity data (i.e. data available in Landscape deployment wizard, "Connectivity" -> "Connectors") for use in Landscape report. | 0|i0101b: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-434 | VNMD-423 Landscape report GUI integration |
Sub-task | blocked | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/08/16 12:24 PM | 12/02/17 02:29 PM | 0 | VNMD-410 | Integrate generating landscape report into Vnomic app GUI. | 0|i01013: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-433 | VNMD-423 Landscapes' connectivity report section |
Sub-task | blocked | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/08/16 12:23 PM | 12/02/17 02:29 PM | 0 | VNMD-435 | Connectivity between landscapes. | 0|i0100v: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-432 | VNMD-423 Landscapes' overview report section |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/08/16 12:20 PM | 27/08/16 03:30 PM | 27/08/16 03:30 PM | 26/08/16 | 0 | Hierarchy of landscapes and deployments in a given landscapes with links to deployment reports for each deployment. | 0|i0100n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-431 | VNMD-423 Landscape report POC |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/08/16 12:14 PM | 25/08/16 12:18 PM | 25/08/16 12:18 PM | 25/08/16 | 0 | Data needed to populate report sections, constructing hierarchy of landscape nodes and deployments. | 0|i0100f: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-423 | Report containing all deployments in a landscape |
Story | blocked | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 17/08/16 12:35 PM | 12/02/17 02:29 PM | 0 | VNMD-431, VNMD-432, VNMD-433, VNMD-434 | ACI | Reporting | 0|i00m6n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-422 | VNMD-175 Configurator Settings report section - support for retrieving attribute labels, units and masking values for password attributes |
Sub-task | Backlog | Medium | Unresolved | Radek Dvorak | Michal Siemaszko | Michal Siemaszko | 17/08/16 12:24 PM | 07/11/16 04:25 AM | Reporting | 2 | VNMD-358 | As discussed in May/June, to complete Configurator Settings report section, support for retrieving attribute labels, units and masking values for password attributes is needed. | ACI | 0|i00m6f: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-419 | Report containing all deployments for a customer |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 14/08/16 10:50 PM | 27/08/16 03:30 PM | 27/08/16 03:30 PM | Reporting | 2 | Create a single report that includes all deployments for a single customer. Need to discuss further but here are some ideas:
1) Title page showing customer information and listing deployment names in the customer. 2) Network and server information contains networks and servers from all deployments. 3) For each deployment include the same per deployment report information. |
ACI | Reporting | 0|i00kmv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-406 | Wrong description for 'ServiceUndeploymentStartedEvent' |
Finding | Done | Medium | Done | Radek Dvorak | Michal Siemaszko | Michal Siemaszko | 05/08/16 05:18 AM | 08/08/16 05:16 AM | 08/08/16 05:16 AM | 0 | Deployments_Events.png | Deployments -> Events window -> 'ServiceUndeploymentStartedEvent' description is wrong, it should read '...started'. Attached is screenshot. | ACI | 0|i00grr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-394 | Camel - RabbitMQ integration into Vnomic application - Phase 1 - Set up branch |
Task | Done | Medium | Done | Radek Dvorak | Michal Siemaszko | Michal Siemaszko | 14/07/16 12:51 PM | 20/02/17 01:59 PM | 15/07/16 08:19 AM | 2 | VNMD-387 | Set up separate branch to be used for Camel - RabbitMQ integration into Vnomic application | ACI | ESB upgrade | 0|i007y7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-391 | VNMD-381 Camel - RabbitMQ integration into Vnomic application - Phase 2 |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/07/16 08:03 AM | 31/08/16 09:44 AM | 31/08/16 09:44 AM | 01/09/16 | 2 | Integrate Camel - RabbitMQ solution into Vnomic App. Second phase is to resolve any compile dependencies, so that Vnomic app can be compiled. | ACI | 0|i007vj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-387 | VNMD-381 Camel - RabbitMQ integration into Vnomic application - Phase 1 |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/07/16 08:43 AM | 16/08/16 02:50 PM | 16/08/16 02:50 PM | 17/08/16 | 2 | camel-blueprint.2.10.7.png camel-core-osgi.2.10.7.png camel-core.2.10.7.png camel-cxf-transport.2.10.7.png camel-cxf.2.10.7.png camel-jms.2.10.7.png camel-spring-security.2.10.7.png camel-spring.2.10.7.png org.eclipse.gemini.blueprint.core.2.0.0.RELEASE.png org.eclipse.gemini.blueprint.extender.2.0.0.RELEASE.png org.eclipse.gemini.blueprint.io.2.0.0.RELEASE.png org.eclipse.gemini.blueprint.mock.2.0.0.RELEASE.png org.eclipse.gemini.blueprint.test.2.0.0.RELEASE.png org.springframework.aop.3.0.7.RELEASE.png org.springframework.aspects.3.0.7.RELEASE.png org.springframework.beans.3.0.7.RELEASE.png org.springframework.context.3.0.7.RELEASE.png org.springframework.context.support.3.0.7.RELEASE.png org.springframework.core.3.0.7.RELEASE.png org.springframework.expression.3.0.7.RELEASE.png org.springframework.jdbc.3.0.7.RELEASE.png org.springframework.jms.3.0.7.RELEASE.png org.springframework.osgi.core.1.2.1.png org.springframework.osgi.extender.1.2.1.png org.springframework.osgi.io.1.2.1.png org.springframework.osgi.web.1.2.1.png org.springframework.security.acls.3.1.4.RELEASE.png org.springframework.security.config.3.1.4.RELEASE.png org.springframework.security.core.3.1.4.RELEASE.png org.springframework.security.web.3.1.4.RELEASE.png org.springframework.test.3.0.7.RELEASE.png org.springframework.transaction.3.0.7.RELEASE.png org.springframework.web.3.0.7.RELEASE.png | 57600 | 86400 | 0% | VNMD-394 | Integrate Camel - RabbitMQ solution into Vnomic App. First phase it verify all updated and new dependencies resolve.
Further development will proceed on a separate branch and new versions / copies of target platform, Ant build scripts and build launcher, i.e. based on /com.virtunomic.releng.target_38/linux-gtk-x86_64/build-designer-linux-gtk-x86_64.launch /com.virtunomic.releng.target_38/linux-gtk-x86_64/designer-linux-gtk-x86_64.target /com.virtunomic.releng.target_38/build.xml |
0% | 0% | 86400 | 57600 | 0|i007pb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-382 | VNMD-381 Camel - RabbitMQ integration proof of concept |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/07/16 05:45 AM | 14/07/16 12:56 PM | 14/07/16 08:06 AM | 2 | Communication between Camel and RabbitMQ using Camel AMQP component with Spring (3.0.7) and Camel (2.10.7) versions used in Vnomic App does not work.
Verify Camel and RabbitMQ can be integrated using latest versions of respective frameworks and/or appropriate alternatives/replacements. |
0|i0072n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-381 | Camel - RabbitMQ integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/07/16 05:44 AM | 05/01/17 01:14 PM | 0 | VNMD-382, VNMD-387, VNMD-391, VNMD-436, VNMD-600, VNMD-601, VNMD-602, VNMD-603, VNMD-604, VNMD-605 | 0% | 86400 | 57600 | Event Driven Capability | 0|i0072f: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-380 | Riemann - RabbitMQ integration |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/07/16 05:43 AM | 05/04/17 02:37 PM | 0 | Integrate Riemann with RabbitMQ so events from Riemann are sent to RabbitMQ | Event Driven Capability | 0|i00727: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-379 | Riemann client |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/07/16 05:43 AM | 11/07/16 05:46 AM | 11/07/16 05:44 AM | 0 | OSGify Riemann client Java bundle, integrate with Vnomic app. | Event Driven Capability | 0|i0071z: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-378 | Event Driven Capability |
Epic | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/07/16 05:42 AM | 12/03/17 10:46 AM | 0 | Event driven capabilities for Vnomic app | ghx-label-12 | Event Driven Capability | To Do | 0|i0071r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-341 | Duplicate IP check during provisioning |
Task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 30/05/16 11:15 AM | 07/06/16 01:07 PM | 07/06/16 01:07 PM | 0 | VNMD-130 | Sometimes servers are not deprovisioned (cleaned up) or IP address are mismanaged causing duplicate address scenario where a newly provisioned server is allocated an IP address (expected to be unused). The deployment automation will connect via SSH and will be connected to the wrong server. The objective is to add a check which verifies the expected MAC address for each interface in the deployed server's OS.
MAC addresses are typically not assigned until the new server is provisioned. Once the server is provisioned, obtain the MAC address for each interface, then connect to the OS to verify the correct MAC address is used for each interface. If not, report an error which indicates the MAC addresses which are incorrect. |
0|i0037r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-340 | Scripts for large api XSDs to java generation using xmlbeans |
Task | Done | Medium | Fixed | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 24/05/16 04:25 PM | 07/06/16 12:32 PM | 07/06/16 12:32 PM | 0 | Platform target uses patched version of xmlbeans to avoid index size limitations.
Generation scripts in xsd hosting bundles should emit java for the given xsd using the patched xmlbeans version and update used jars. The path to xmlbean jars can be passed as a param in script launchers, workspace location variable available in the launcher can be used as a base. |
0|i00367: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-338 | Save reports to content repository |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/05/16 08:51 AM | 25/05/16 03:35 PM | 25/05/16 03:35 PM | 0 | Reporting | 0|i0034f: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-337 | Generate report via scheduler service |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/05/16 08:49 AM | 07/06/16 01:46 PM | 07/06/16 01:46 PM | 0 | Reporting | 0|i00347: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-324 | Activity log report |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/05/16 02:57 PM | 07/06/16 02:36 PM | 07/06/16 02:36 PM | 0 | As a Vnomic user,
I want to generate report with all data available in activity monitor So that I can easily review it *Given* I have an instance of Vnomic Console opened *And* I navigate to Deployments section *And* I select Service Deployment event *And* I click Activity Monitor button *When* I select "Generate report" menu *And* I click one of the available report formats *Then* a report with activity data is generated |
Reporting | 0|i002zr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-282 | VNMD-259 Integrate logging in Vnomic app with selected log management system |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/03/16 10:21 AM | 05/04/16 01:07 PM | 05/04/16 01:07 PM | 1 | 0|i002mf: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-281 | VNMD-259 Integrate "Pax Logging" with Vnomic app |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/03/16 10:21 AM | 05/04/16 01:07 PM | 05/04/16 01:02 PM | 1 | 0|i002m7: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-280 | VNMD-259 Research and choose solution for unifying logging |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/03/16 10:20 AM | 14/03/16 10:23 AM | 14/03/16 10:23 AM | 1 | 0|i002lz: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-263 | Repeated execution of generation of self signed cert fails |
Finding | Done | Medium | Fixed | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 03/03/16 08:21 AM | 04/03/16 11:13 AM | 04/03/16 11:13 AM | System Configuration | 1 | [vnomic@dsc_1 dsc]$ ./vn security-cert-create --common-name "Vnomic default certificate" --size 2048 --country US --state Californa --locality Sunnyvale --organization "Vnomic" --unit Vnmd
Creating and installing a custom self-signed digital certificate Error generating certificate [vnomic@dsc_1 dsc]$ Key pair not generated, alias <mykey> already exists |
0|i002hj: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-259 | Unified logging for Vnomic app |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 02/03/16 01:30 PM | 05/04/16 01:08 PM | 05/04/16 01:08 PM | 1 | VNMD-280, VNMD-281, VNMD-282 | VNMD-237 | Currently, in Vnomic app messages are logged using at least five different frameworks ("log4j", "logback", "commons-logging", "java.util.logging" in addition to "org.osgi.service.log"). In order to satisfy the requirement of publishing logs from Vnomic app to log management system, these need to be unified / bridged and their configuration controlled in one place. | 0|i002gf: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-187 | Configuring loggers so they emit content to correct location and have correct behavior |
Task | Backlog | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 25/10/15 04:10 PM | 07/07/16 10:56 AM | System Configuration | 3 | When running deployment jobs we se console messages like:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. This is because the logs have not been explicitly configured. We need to address this and ensure we log to reasonable locations. In the past we put everything in ./eclipse/.../logs/integrated.log. It may be more appropriate to separate these into different files (or maybe not). The first step is to take inventory of what logging is happening and needs to be configured. We should ensure at least 48 hours of space is available AND that we roll over to avoid filling up the filesystem. |
0|i001nr: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-182 | VNMD-175 Provide drop-down menu with clickable list of available report formats to generate report in |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:39 AM | 09/10/15 10:01 AM | 09/10/15 10:01 AM | 1 | 0|i001jz: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-181 | VNMD-175 Incorporate vector version of Vnomic logo into report layout |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:36 AM | 11/05/16 03:00 PM | 11/05/16 03:00 PM | 1 | 0|i001jr: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-180 | Generate report as last step of service deployment |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:31 AM | 13/07/16 07:50 AM | 1 | Reporting | 0|i001jj: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-179 | Display progress information while generating report |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:30 AM | 27/08/16 03:31 PM | 27/08/16 03:31 PM | 1 | Reporting | 0|i001jb: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-178 | VNMD-175 Generate hyperlinked table of contents as part of report |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:30 AM | 20/05/16 08:28 AM | 20/05/16 08:28 AM | 1 | 0|i001j3: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-177 | VNMD-175 Add remaining sections/tables for deployment info report |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:30 AM | 07/11/16 04:23 AM | 07/11/16 04:23 AM | 1 | 186_has2_1_deployments_connectivity_concrete.png 186_has2_1_deployments_connectivity_logical_admin.png 186_has2_1_deployments_connectors_exposed-servers.png 186_has2_1_deployments_connectors_local-connections.png 186_has2_1_deployments_deployment-profile_policies.png 186_has2_1_deployments_resources_allocations.png 186_has2_1_deployments_resources_capacity-status.png 186_has2_1_deployments_resources_detail.png 186_has2_1_deployments_servers_tier-endpoint-group.png 186_has2_1_deployments_servers_tier-ip-routes.png 186_has2_1_deployments_servers_tier-network.png 186_has2_1_deployments_servers_vm-ip-addresses.png 186_has2_1_deployments_service-topology_components.png 186_has2_1_deployments_service-topology_dependencies.png 186_has2_1_deployments_storage.png | 0|i001iv: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-176 | VNMD-175 Create list of & mockups of remaining sections/tables for deployment info report |
Sub-task | Done | Medium | Done | Derek Palma | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:30 AM | 07/11/16 04:23 AM | 07/11/16 04:23 AM | 1 | 0|i001in: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-175 | Deployment info report |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:23 AM | 13/07/16 07:50 AM | 1 | VNMD-176, VNMD-177, VNMD-178, VNMD-181, VNMD-182, VNMD-422 | As a Vnomic user,
I want to generate report with all relevant deployment information So that I can easily review it *Given* I have an instance of Vnomic Console opened *And* I navigate to Deployments section *When* I select "Generate report" menu *And* I click one of the available report formats *Then* a report with all relevant deployment information is generated |
Reporting | 0|i001if: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-174 | Reporting - solution and implementation |
Epic | In Progress | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 08/10/15 07:21 AM | 05/05/17 03:33 PM | 1 | ghx-label-3 | Reporting | To Do | 0|i001i7: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-163 | VNMD-161 Generating reports in Microsoft Excel format |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 28/09/15 01:26 PM | 08/10/15 06:59 AM | 08/10/15 06:59 AM | 1 | 0|i001ev: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-162 | VNMD-161 Generating reports in PDF & Microsoft Word formats |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 28/09/15 01:26 PM | 08/10/15 06:59 AM | 08/10/15 06:59 AM | 1 | 0|i001en: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-161 | Reporting engine solution - research & POC |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 28/09/15 01:23 PM | 08/10/15 07:21 AM | 08/10/15 06:59 AM | 1 | Vn_reportingEngine_solutionsComparison.png | VNMD-162, VNMD-163 | Research reporting engine solution to be utilized for generating reports in PDF, Microsoft Word and, preferably, Microsoft Excel formats. Implement proof-of-concept/prototype. | Reporting | 0|i001ef: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-151 | Update plan executor automated tests |
Story | Backlog | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 23/09/15 10:50 AM | 07/07/16 10:56 AM | 1 | Extend 'vn_singlenode_autotest' to add support for running update plan executor automated tests of selected service deployments.
Determine changes/enhancements needed, implement. Start with automating NTP service deployment test. Use number of activities in total, number of activities with errors as proof a given service deployment success. |
0|i001c7: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-150 | VNMD-82 Variables used in scripts and puppet classes should be visible in activity monitor detail panel |
Sub-task | Backlog | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 23/09/15 10:43 AM | 07/07/16 10:56 AM | UpdatePlanExecutor | 1 | For execute script and apply puppet class operations, variables passed to and used inside these should be made visible in activity monitor detail panel - eg. as additional tab, next to "Script" or "Puppet class" tabs recently added. | 0|i001bz: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-149 | GIT proof of concept |
Story | Backlog | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 23/09/15 10:10 AM | 07/07/16 10:56 AM | 1 | In order to assess the impact of transition to Git as SCM - CVS being used so far - a proof of concept project needs to be created.
GIT server would need to be set up, repository created, all of the modules that constitute Vnomic app would be need to be checked in to the newly created repository, new versions of map files and build scripts created to fetch these using GIT and build the entire application. |
0|i001br: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-148 | VNMD-82 Remove obsolete status messages |
Sub-task | Backlog | Medium | Unresolved | Derek Palma | Michal Siemaszko | Michal Siemaszko | 23/09/15 09:54 AM | 07/07/16 10:56 AM | UpdatePlanExecutor | 1 | Remove status messages such as:
* "Failed to achieve running state for: com.virtunomic.model.sap.impl ... " * other? |
0|i001bj: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-147 | VNMD-82 Display task progress in activity monitor |
Sub-task | Backlog | Medium | Unresolved | Derek Palma | Michal Siemaszko | Michal Siemaszko | 23/09/15 08:22 AM | 07/07/16 10:56 AM | 1 | VNMD-46, VNMD-113 | Description: Currently, for some of the methods, task progress is being calculated via call to `com.virtunomic.model.content.packager.VirtualMachineUpdateDomain.waitForTaskToComplete(Task, ITaskActivityMonitorExt, String)` method. To have this information available for other methods, which already have message set upon activity start, room for this extra information would have to be made.
Suggestion is to use "Status" column of activity monitor to display task progress - i.e. in addition to existing statuses, that is "Failed", "Success", "Running" - have "Progress" status with numerical value displaying task progress. |
0|i001bb: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-129 | Ensure there's only one way to set activity details message |
Task | Backlog | Medium | Unresolved | Radek Dvorak | Michal Siemaszko | Michal Siemaszko | 10/09/15 10:52 AM | 07/07/16 10:56 AM | 1 | Ensure there's only one way to set activity details message - currently, activity details message is set in at least 3 different ways at the start of a given activity, i.e.:
1) activityInfo.setDetails(details); 2) activityInfo.setInitialMessage(details); 3) getMonitor().setStatusMessage(details); Side-effects of this are: missing info in "Recent jobs" tab (`PendingJobsDUITable`), even though complete information is visible via Activity Monitor Viewer, duplicated info when using both methods at the same time, etc. Contract should be enforced via interface, refactor of existing classes needed. |
0|i0017b: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-123 | VNMD-82 Update plan executor must know context in which it is run |
Sub-task | Backlog | Medium | Unresolved | Derek Palma | Michal Siemaszko | Michal Siemaszko | 04/09/15 08:49 AM | 07/07/16 10:56 AM | UpdatePlanExecutor | 1 | VNMD-45 | Update plan executor can be run for both fresh deployments as well as updates of existing deployments - this info must be made available, so operations running as part of a given update plan can vary their behaviour accordingly. | 0|i0015r: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-118 | Move build server to ACI lab |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 01/09/15 07:13 AM | 04/09/15 03:04 PM | 04/09/15 03:04 PM | 1 | Because of continuing infrastructure problems in VCE lab, which affect how long builds take, Hudson must be moved to ACI lab. Configure VM, install, move data from VCE Hudson instance. | 0|i0014f: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-112 | Provide access to results from NetApp API calls |
Story | Done | Medium | Done | Derek Palma | Michal Siemaszko | Michal Siemaszko | 29/08/15 03:22 PM | 30/06/17 06:26 AM | 30/06/17 06:26 AM | 30/06/17 06:26 AM | 1 | MOD-480 | In `com.virtunomic.netapp.client.nmsdk.NetAppCDOTClient`, results from NetApp API invocations should be accessible for calling classes (e.g. `com.virtunomic.model.content.packager.CDOTSupport`) | NetApp Storage Support | 0|i00127: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-106 | Ensure appropriate data is available in update operations so that relevant target information can be constructed |
Story | Backlog | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 25/08/15 12:38 PM | 07/07/16 10:56 AM | 1 | Currently, target type and label is constructed based on subject extracted from update operation object. However, relevant target information (i.e. 'Target' column displayed in 'Activity Monitor' viewer, "target" data structure in "activity" table where deployment data is stored) cannot be constructed from data available in that object as is. Ensure appropriate data is available in the model passed to these operations. | 0|i0010v: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-100 | VNMD-81 Allow retrieving results from resource provisioning API calls |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/08/15 08:10 AM | 29/08/15 05:16 PM | 29/08/15 05:16 PM | UpdatePlanExecutor | 1 | Resource provisioning APIs (such as VSphere, NetApp, etc.) must expose the results of calls to APIs they invoke, so that calling classes such as the XXXSuport classes utilized by UpdatePlanExecutor can retrieve this result data when needed. | 0|i000zb: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-99 | VNMD-81 Expand use of and info provided in property sheets displayed for *UpdateOperation data |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/08/15 08:08 AM | 26/08/15 12:38 PM | 26/08/15 12:38 PM | UpdatePlanExecutor | 1 | Currently, in Activity Monitor viewer, when *UpdateOperation is selected, a property sheet is displayed in 'detail panel' section. In case of exception, the update command which failed must be included in the property sheet, so it's clear which object received the error. | 0|i000z3: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-98 | VNMD-81 Allow multiple tabs in 'detail panel' composite of Activity Monitor viewer |
Sub-task | Done | Medium | Won't Do | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/08/15 08:05 AM | 25/08/15 08:20 AM | 25/08/15 08:20 AM | UpdatePlanExecutor | 1 | VNMD-92 | Allow displaying data in both "Details", "Stdout", "Stderr" tabs as well as adding more tabs (see: VNMD-92) - i.e. all tabs available at the same time in 'detail panel' composite of 'com.virtunomic.console.ui.activity.mon.MonitorViewer' class and ability to switch between them.
Currently, in 'detail panel' when *UpdateOperation is selected, a property sheet is displayed in "Details" tab. For one-step operartions such as "ProvisionTenantUpdateOperation", "ProvisionResourcePoolUpdateOperation", "CreateVolumeOperation", etc. which consist of only one child operation, merging child operation info with parent operation requires ability to display "Stdout" and "Stderr" output from such and switching between them. |
0|i000yv: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-96 | VNMD-81 Remove System.out.message if same information passed to Activity Monitor |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 21/08/15 09:15 AM | 25/08/15 03:39 PM | 25/08/15 03:39 PM | UpdatePlanExecutor | 1 | Idea is to transition to Activity Monitor for all status messages. Already many emitted to the console are redundant and should be removed. | 0|i000xj: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-92 | Display executed script in Activity Monitor viewer |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 19/08/15 08:08 AM | 29/08/15 02:58 PM | 29/08/15 02:57 PM | 1 | VNMD-98 | Add a separate tab with content of executed script to 'detail panel' composite of 'com.virtunomic.console.ui.activity.mon.MonitorViewer' class. | 0|i000wn: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-91 | VNMD-81 Provisioning update operations should show meaningful status |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 18/08/15 08:40 PM | 26/08/15 09:18 AM | 26/08/15 09:18 AM | UpdatePlanExecutor | 1 | UpdatePlanExecutor calls into XXXSuport classes to invoke resource provisioning operations. Each operations should report meaningful status. E.g. provision virtual machine including the name of the virtual machine, the tier and other meaningful context. Different kinds of resources will require different information and status. It's important to take a general approach for this.
Note that these operations appear under the node Deployment Provision in the Activity Monitor. The objective is to make records under this node meaningful. |
0|i000wf: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-83 | Deploing Service from Service Catalog does not pick up selected service |
Finding | Backlog | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 14/08/15 03:27 PM | 07/07/16 10:56 AM | 1 | Please see attached screencast MP4 for visual / more info. | 0|i000un: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-81 | Update operation status improvement |
Story | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 11/08/15 07:28 AM | 29/08/15 05:16 PM | 29/08/15 05:16 PM | UpdatePlanExecutor | 1 | VNMD-10, VNMD-41, VNMD-43, VNMD-50, VNMD-51, VNMD-52, VNMD-91, VNMD-96, VNMD-98, VNMD-99, VNMD-100 | Improve the quality of information reported for update operations in the Activity Monitor. | 0|i000u7: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-80 | VNMD-36 Copy content between vSphere datastores |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/08/15 07:27 AM | 08/08/15 12:40 PM | 08/08/15 12:40 PM | 1 | 0|i000tz: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-65 | Integrate SWAGGER for REST documentation/consumability |
Task | Selected for Development | Medium | Unresolved | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 03/08/15 03:44 AM | 24/06/17 05:22 AM | 22/06/17 06:18 AM | 1 | Research topics to be done before starting implementation:
# Research if SWAGGER/Open API is the right solution or not # Dependencies required and if this can work in our target |
0|i000q7: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-52 | VNMD-81 State changes should be able to show command or script |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 31/07/15 02:24 PM | 14/08/15 05:26 PM | 14/08/15 05:26 PM | UpdatePlanExecutor | 2 | State change is a special kind of update. Need to display more meaningful information, e.g. script or command causing the state change. | 0|i000mv: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-51 | VNMD-81 Phase and target of execution should be displayed |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 31/07/15 02:23 PM | 17/08/15 01:11 PM | 17/08/15 01:11 PM | UpdatePlanExecutor | 2 | 0|i000mn: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-50 | VNMD-81 Provide location of script in target for error message |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 31/07/15 02:22 PM | 14/08/15 01:32 PM | 14/08/15 01:32 PM | UpdatePlanExecutor | 2 | Activity monitor should include the location of the script in the target, in addition to just the name of the script being executed. <script>@<host><path> | 0|i000mf: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-43 | VNMD-81 All activities should have messages with right context |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 31/07/15 11:34 AM | 14/08/15 11:18 AM | 14/08/15 11:18 AM | UpdatePlanExecutor | 2 | 0|i000kv: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-41 | VNMD-81 Should be clear which script is executing on which node for which state |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 31/07/15 11:32 AM | 14/08/15 05:25 PM | 14/08/15 05:25 PM | UpdatePlanExecutor | 2 | 0|i000kf: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-39 | VNMD-36 Upload content to vsphere datastore |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 30/07/15 05:38 AM | 07/08/15 02:56 PM | 07/08/15 02:56 PM | 2 | 0|i000jz: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-38 | VNMD-36 Boot SVM content upload |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 30/07/15 05:33 AM | 12/08/15 04:05 PM | 12/08/15 04:05 PM | 2 | 0|i000jr: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-36 | Resource Deployer |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 28/07/15 03:52 PM | 25/08/15 09:29 AM | 25/08/15 09:29 AM | 1 | VNMD-32, VNMD-38, VNMD-39, VNMD-80 | Provision and deploy resource given its type and metadata. | 83% | 36000 | 7200 | 57600 | 0|i000j3: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-33 | Make Vnomic vApp cluster configuration available to nodes via Config Server node / ZooKeeper |
Story | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 21/07/15 02:51 PM | 29/07/15 01:17 PM | 28/07/15 02:12 PM | 1 | 57600 | 14400 | 14400 | 25% | 50% | 50% | 14400 | 14400 | 57600 | 0|i000bj: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-32 | VNMD-36 OVF package importer |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 21/07/15 02:51 PM | 30/07/15 06:10 PM | 27/07/15 11:21 AM | 1 | 57600 | 7200 | 36000 | 62% | 83% | 83% | 36000 | 7200 | 57600 | 0|i000br: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-25 | Continuous integr. build |
Task | Done | Medium | Fixed | Michal Siemaszko | Arivalagan Kaliyaperumal | Arivalagan Kaliyaperumal | 03/07/15 01:53 AM | 31/07/15 03:37 PM | 31/07/15 03:37 PM | 1 | 0|i0001b: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Vn-MD | VNMD-10 | VNMD-81 Don't log errors for failed updates |
Sub-task | Done | Medium | Fixed | Michal Siemaszko | Derek Palma | Derek Palma | 23/07/15 07:49 PM | 17/08/15 03:53 PM | 17/08/15 03:53 PM | UpdatePlanExecutor | 2 | Activity monitor captures status effectively. Errors were logged back when thee was not activity monitor. | 0|i000db: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-517 | MOD-446 Customize Windows VM during provisioning |
Sub-task | Selected for Development | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 30/06/17 07:23 AM | 30/06/17 07:24 AM | 30/06/17 07:24 AM | 1 | - modify OS version requirement for selected service template (Tosca Demo DB Client)
- verify Windows specific customization path is taken during provisioning - verify Windows customization code works correctly - debug/modify where necessary - verify Windows VM boots correctly |
0|i07qgv: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-516 | MOD-446 Prepare VM image for use by Vnomic automation |
Sub-task | In Progress | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 30/06/17 07:16 AM | 30/06/17 07:24 AM | 30/06/17 07:24 AM | 1 | - export VM image as OVF
- copy to artifact repository (/vn_repo/mnt1/3rdParty/vm_images) - create bundle metadata - reference the newly created bundle by its ID in selected service template (Tosca Demo DB Client) - verify VM image is used when running service deployment |
0|i07qgn: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-515 | vSphere Client detailed API information |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 27/06/17 08:27 AM | 30/06/17 11:04 AM | 30/06/17 11:04 AM | 0 | Client API tracing | 0|i07pr3: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-514 | APIC Client detailed API information |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 27/06/17 08:27 AM | 30/06/17 11:04 AM | 30/06/17 11:04 AM | 0 | Client API tracing | 0|i07pqv: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-507 | ASA Client detailed API information |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 23/06/17 09:57 AM | 27/06/17 08:27 AM | 27/06/17 06:42 AM | 27/06/17 06:42 AM | 1 | Client API tracing | 0|i07p5j: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-500 | A10 Client detailed API information |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 31/05/17 08:07 AM | 27/06/17 06:37 AM | 27/06/17 06:37 AM | 27/06/17 06:37 AM | 30/06/17 | 0 | APIC client should support capture of requests and responses from API.
Failed requests should include request and response data as close as possible to the syntax of the API. |
Client API tracing | 0|i07llz: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-499 | UCSM Client detailed API information |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 31/05/17 08:05 AM | 27/06/17 06:40 AM | 27/06/17 06:39 AM | 27/06/17 06:39 AM | 30/06/17 | 0 | UCSM client should support capture of requests and responses from API.
Failed requests should include request and response data as close as possible to the syntax of the API. |
Client API tracing | 0|i07llr: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-493 | Code 654377006; Out of Memory |
Bug | Done | Highest | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/05/17 09:12 AM | 02/06/17 11:12 AM | 02/06/17 11:12 AM | 02/06/17 11:12 AM | 30/06/17 | 0 | A10 Support | 0|i06y2v: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-492 | Code 754974733; Partition id has been used, please choose a different id |
Bug | Done | Highest | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/05/17 09:12 AM | 15/05/17 10:34 AM | 15/05/17 10:34 AM | 1 | A10 Support | 0|i06y2n: | 1 | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-489 | A10 Client connect and read timeouts |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 18/04/17 01:25 PM | 24/04/17 01:44 PM | 24/04/17 01:44 PM | 1 | Connect timeout should be 5 secs.
Read timeout should be 1 min. |
Client connect and read timeouts | 0|i04u87: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-487 | A10 client should validate server certificate |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 10/04/17 11:14 AM | 24/04/17 01:32 PM | 24/04/17 01:32 PM | 1 | Client security | 0|i04m8n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-486 | NetApp Client connect and read timeouts |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/04/17 02:29 PM | 15/05/17 01:26 PM | 15/05/17 01:26 PM | Capability Providers | 31/05/17 | 0 | Connect timeout should be 5 secs.
Read timeout should be 1 min. |
Client connect and read timeouts | 0|i04e1r: | NTP Service 1 Tier | CTL Lab Readiness-April, CTL Lab Readiness-May | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-485 | UCSM Client connect and read timeouts |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/04/17 02:21 PM | 17/04/17 12:25 PM | 17/04/17 12:25 PM | Capability Providers | 30/04/17 | 0 | Connect timeout should be 5 secs.
Read timeout should be 1 min. |
Client connect and read timeouts | 0|i04e1j: | NTP Service 1 Tier | CTL Lab Readiness-April | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-484 | APIC Client connect and read timeouts |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/04/17 02:21 PM | 17/04/17 12:24 PM | 17/04/17 12:24 PM | Capability Providers | 30/04/17 | 0 | Connect timeout should be 5 secs.
Read timeout should be 1 min. |
Client connect and read timeouts | 0|i04e1b: | NTP Service 1 Tier | CTL Lab Readiness-April | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-480 | NetApp Client detailed API information |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 06/04/17 01:40 PM | 27/06/17 06:41 AM | 27/06/17 06:41 AM | 27/06/17 06:41 AM | Capability Providers | 30/06/17 | 0 | VNMD-112 | CDOT API should clearly show parameters of API call for failure as well as target endpoint. | Client API tracing | 0|i04dyn: | NTP Service 1 Tier | CTL Lab Readiness-April, CTL Lab Readiness-May, CTL Lab Readiness-June | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-463 | A10 device REST client implementation for automation |
Story | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 13/03/17 08:17 AM | 29/06/17 06:24 AM | 29/06/17 06:24 AM | 30/06/17 | 0 | QA-43009 | Implement the REST APIs required by the automation workflow in a Java client.
Devices are available in Raiders Lab: https://vnomic.atlassian.net/wiki/display/MOD/Raiders+Lab |
A10 Support | 0|i03b3j: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-458 | Provision via vSphere multiple Windows VMs with WinRM configured and AD DNS feature installed |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 05/03/17 02:04 PM | 30/06/17 07:24 AM | 07/04/17 11:54 AM | 07/04/17 11:54 AM | 30/04/17 | 2 | This is necessary to test the root / delegated zone PowerShell commands on VMs provisioned via vSphere. | DNS using Active Directory | 0|i039n3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-457 | Provision via Azure multiple Windows VMs with WinRM configured and AD DNS feature installed |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 05/03/17 02:03 PM | 12/04/17 12:55 PM | 12/04/17 12:55 PM | 1 | For provisioning in Azure cloud, "resource loops" based template provisions 1-n VMs, then via CustomScriptExtension configures WinRM and installs AD DNS features & tools.
Remaining configuration, depending on VM role (root, delegated child zone, domain member) is done via PowerShell invoked via WinRM (AD DNS Java client). Customize ARM template to provision two VMs - parent and child - and configure them via CustomScriptExtension, rest via AD DNS Java client in Unit test. |
DNS using Active Directory | 0|i039mv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-456 | Provision via Azure Windows VM with Active Directory integrated DNS server |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 21/02/17 02:24 PM | 05/03/17 02:02 PM | 22/02/17 01:04 PM | 28/02/17 | 1 | * Azure template for Active Directory server - check availability, otherwise create.
* VM extension / PowerShell script for integrating DNS service with AD - check availability, otherwise create |
DNS using Active Directory | 0|i035av: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-455 | IOperatingSystemAccess` methods applicable for remote access to Windows OS |
Story | blocked | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/02/17 11:13 AM | 30/06/17 07:24 AM | 14/05/17 06:08 PM | 30/06/17 | 2 | Analyze which part of the interface will be applicable to Windows. Determine which methods will be applicable using the WinRm approach for collecting WMI objects, which for Windows DSC push model. Decide if refactoring into common (to both Linux and Windows) and OS specific versions is needed. | Windows Suppport | 0|i0001a:i60001zzzzzz | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-449 | MOD-446 Sysprep the images and verify they are "Vnomic ready" |
Sub-task | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 12/02/17 06:04 PM | 14/05/17 06:10 PM | 30/06/17 | 0 | 0|i034h3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-448 | MOD-446 Install all the components on the Windows VM image required for Vnomic |
Sub-task | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 12/02/17 06:02 PM | 14/05/17 06:09 PM | 30/06/17 | 0 | Document this procedure | 0|i034gv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-441 | Automation to support Windows DSC push model |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/02/17 02:36 PM | 20/02/17 11:10 AM | 20/02/17 11:10 AM | 28/02/17 | 1 | Automated installation of Azure PowerShell module, automated/scripted Azure account login, recursive staging and retrieval of content via Azure Storage | Windows Desired State Configuration Support | 0|i034ef: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-440 | AD client with support for DNS programming |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 12/02/17 01:05 PM | 12/04/17 12:35 PM | 12/04/17 12:35 PM | Capability Providers | 30/04/17 | 0 | MOD-439 | The client needs to support the following:
# Creating a sub-zone (e.g. subzone1.abc.com) # Setting the name servers for the parent zone (abc.com) # Setting the IPs and names of all the servers in the topology |
DNS using Active Directory | 0|i0001a:i60001zzzv | NTP Service 1 Tier | CTL Lab Readiness, CTL Lab Readiness-April | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-439 | Research AD APIs for DNS programmability |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 12/02/17 01:01 PM | 21/02/17 02:23 PM | 21/02/17 02:23 PM | 28/02/17 | 0 | MOD-440 | Check if available AD APIs support DNS programmability for:
# Creating a sub-zone (e.g. subzone1.abc.com) # Setting the name servers for the parent zone (abc.com) # Setting the IPs and names of all the servers in the topology |
DNS using Active Directory | 0|i034bz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-436 | Install Chocolatey via PowerShell |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/02/17 10:22 AM | 12/02/17 06:12 PM | 12/02/17 02:30 PM | 1 | MOD-446 | Windows Suppport | 0|i032pr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-426 | Execute Windows DSC in push mode remotely from Linux |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 05/02/17 09:26 PM | 17/02/17 08:34 AM | 11/02/17 11:07 AM | 28/02/17 | 0 | MOD-386 | Create a simple DSC script and execute it using Start-DSCConfiguration (which is just a PowerShell script) | Windows Desired State Configuration Support | 0|i0323z: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-425 | Execution of PowerShell scripts remotely from Linux |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 05/02/17 09:24 PM | 20/02/17 11:10 AM | 20/02/17 11:10 AM | 28/02/17 | 0 | MOD-446 | Copy one or more PowerShell scripts or data files to the Windows target.
Execute the main PowerShell script and send the results back via to Linux. 1. Our code base uses scripts kept in /com.virtunomic.config-feature/root/virtunomic/agent/windows a. The Windows specific code calls the exec-ps-script.bat script to execute powershell on the target. 2. This is used in: com.virtunomic.model.support.backing.WindowsFileSystemContentServiceProvider com.virtunomic.model.support.backing.WindowsNetworkContentProvider com.virtunomic.model.support.backing.WindowsOnlineDeployedDiskProvider com.virtunomic.model.support.backing.WindowsProductManagerContentServiceProvider 3. We need to support this approach, as in WindowsNetworkContentProvider.load() try { String windowsTmpDir = "/virtunomic/tmp"; String scriptName = "nics.ps1"; String remotePath = WindowsConstants.AGENT_BASE_DIR + "/tmp/" + scriptName; String localPath = WindowsConstants.LOCAL_BASE_DIR + "/callables/" + scriptName; operatingSystemAccess.copyLocalToTarget(localPath, remotePath); String outFile = "-path /virtunomic/tmp/out.json"; remoteCommand = "cd " + WindowsConstants.AGENT_TMP_DIR + "; " + WindowsConstants.AGENT_BASE_DIR + "/exec-ps-script.bat " + windowsTmpDir + "/" + scriptName + " " + outFile; execResult = operatingSystemAccess.executeTargetCommand(remoteCommand); if (!execResult.isSuccess()) { execResult.dumpOutput(); } localPath = "/tmp/virtunomic/out.json"; remotePath = WindowsConstants.AGENT_BASE_DIR + "/tmp/out.json"; operatingSystemAccess.copyTargetToLocal(remotePath, localPath); if (!execResult.isSuccess()) { execResult.dumpOutput(); } URI fileURI = URI.createFileURI(localPath); List<EObject> nicEObjects = EcoreJsonMarshaller.loadJsonContent(fileURI, WindowsConstants.TYPE_MAPPING); for (EObject nicEObject : nicEObjects) { Windows_Win32_NetworkAdapterConfiguration nic = (Windows_Win32_NetworkAdapterConfiguration) nicEObject; nics.add(nic); } } catch (IOException ex) { Log.logError(LOG_CONTEXT, "Failed to get nics for VM: " + vmName, ex); setStatus(Status.Failed); return; } 4. Access to the remote target is via IOperatingSystemAccess. This interface will need to be implemented for Windows to use Windows specific mechanisms. |
Windows Suppport | 0|i0323r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-418 | Java client to invoke WMI over DCOM |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 03/02/17 07:58 AM | 12/02/17 02:47 PM | 12/02/17 02:47 PM | Capability Providers | 28/02/17 | 0 | Research approach for invoking WMI remotely from java client in order to avoid trouble of manually marshaling .Net objects to JSON and back to POJOs.
Determine the communication and credential requirements for the Windows side. |
WinRM Support | 0|i031tr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-386 | Investigate requirements for Windows DSC deployment |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 13/01/17 02:22 PM | 17/02/17 08:34 AM | 17/02/17 08:34 AM | 28/02/17 | 0 | MOD-385, MOD-426 | Determine how Windows DSC can be deployed into a newly provisioned Windows VM.
How can DSC be invoked from the Vnomic runtime? |
Windows Desired State Configuration Support | 0|i02ypr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-385 | Windows Desired State Configuration Support |
Epic | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 13/01/17 02:20 PM | 20/02/17 11:12 AM | 0 | MOD-377, MOD-386, MOD-446 | Windows Desired State Configuration provides a mechanism to do many of the operation Vnomic does on Linux using Puppet. The objective is to figure out how this can be used with Windows.
Useful docs: Main article: https://msdn.microsoft.com/en-us/powershell/dsc/overview On Azure: https://msdn.microsoft.com/en-us/powershell/dsc/azuredsc Invoking with ARM template: https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-extensions-dsc-template |
ghx-label-4 | Windows Desired State Configuration Support | To Do | 0|i02ypj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-384 | Research WinRM libaries for Java |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 13/01/17 02:14 PM | 06/02/17 09:54 AM | 06/02/17 09:54 AM | 0 | Look at the available WinRM implementations in Java.
Do they implement the WinRM protocol in pure Java (and not just load some Windows DLL)? What kind of network connectivity and credentials are required? |
WinRM Support | 0|i02ypb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-383 | WinRM Support |
Epic | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 13/01/17 02:08 PM | 12/02/17 06:11 PM | 12/02/17 02:47 PM | Capability Providers | 0 | MOD-377, MOD-446 | Invocation of WinRM from Vnomic runtime.
Support operations on target WIndows node such as: # Invoke PowerShell script # Invoke WMI API call to get information, set network routes, format disks, etc. Main article: https://msdn.microsoft.com/en-us/library/aa384426(v=vs.85).aspx Powershell remoting is the mechanism used to invoke commands on managed servers PowerShell Remoting uses Windows Remote Management (WinRM), which is the Microsoft implementation of the Web Services for Management (WS-Management) protocol, to allow users to run PowerShell commands on remote computers. You can find more information about using PowerShell Remoting at Running Remote Commands. PowerShell Remoting is not the same as using the ComputerName parameter of a cmdlet to run it on a remote computer, which uses Remote Procedure Call (RPC) as its underlying protocol. |
ghx-label-8 | WinRM Support | To Do | 0|i02yp3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-361 | Provide method to query gateway connection status |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 09/01/17 07:50 AM | 09/01/17 07:50 AM | Capability Providers | 0 | Sometimes gateway connections never reach the connected state. Provide a way to determine the states of VPN connections between a pair of gateways. | Azure Capability Provider | 0|i02y1b: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-357 | MOD-328 Configure read/connect timeouts in vsphere provisioning |
Sub-task | Done | Medium | Done | Michal Siemaszko | Radek Dvorak | Radek Dvorak | 05/01/17 09:48 AM | 09/02/17 07:40 AM | 09/02/17 07:40 AM | 1 | Current version of vijava we use does not allow to set read/connect timeouts before service instance is created (in constructor)
The constructor calls retrieveServiceContent which is impacted by timeouts sets at this point. So far we can set it to ws client only on already created service instance like in code bellow, which is too late: {code:java} WSClient wsc = si.getServerConnection().getVimService().getWsc(); wsc.setConnectTimeout(30*1000); wsc.setReadTimeout(10*1000); {code} Newer api versions should provide specific ServiceInstance constructor to avoid this issue |
0|i02xi7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-354 | Azure Java SDK v.1.0.0-beta4 - inner model ID is not being set, asynchronous deployment fails with NullPointerException |
Bug | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 05/01/17 09:14 AM | 09/01/17 02:11 PM | 09/01/17 02:11 PM | 1 | MOD-353 | Azure Java SDK v.1.0.0-beta4 appears to have a bug in its implementation.
Asynchronous deployment code which worked properly so far (with v. 1.0.0-beta3 most recently) i.e.: deployTemplateServiceCall = azure.deployments() .define(deploymentName) .withExistingResourceGroup(resourceGroupName) .withTemplate(armTemplateJson).withParameters("{}") .withMode(DeploymentMode.INCREMENTAL) .createAsync(deployTemplateServiceCallback); ... now fails with NullPointerException. In constructor of `_com.microsoft.azure.management.resources.implementation.DeploymentImpl_` class, *null* is passed to call: _this.resourceGroupName = ResourceUtils.groupFromResourceId(innerModel.id());_ I.e. ID attribute is not set, yet attempt to extract resource group name is made. Relevant stack trace: _{color:red}Caused by: java.lang.NullPointerException at com.microsoft.azure.management.resources.fluentcore.arm.ResourceId.parseResourceId(ResourceId.java:36) at com.microsoft.azure.management.resources.fluentcore.arm.ResourceUtils.groupFromResourceId(ResourceUtils.java:27) at com.microsoft.azure.management.resources.implementation.DeploymentImpl.<init>(DeploymentImpl.java:56) at com.microsoft.azure.management.resources.implementation.DeploymentsImpl.createFluentModel(DeploymentsImpl.java:111) at com.microsoft.azure.management.resources.implementation.DeploymentsImpl.define(DeploymentsImpl.java:102) at com.microsoft.azure.management.resources.implementation.DeploymentsImpl.define(DeploymentsImpl.java:27) at com.virtunomic.microsoft.azure.client.AzureClient.deployTemplateAsync(AzureClient.java:368) ... 215 more{color}_ Same issue was already present in trunk few weeks ago - reason why we did not use trunk version back then. However, this same issue is still present in released Azure Java SDK libraries, v. 1.0.0-beta4. |
Azure Capability Provider | 0|i02xhj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-353 | Azure Java SDK beta4 upgrade |
Task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 04/01/17 07:00 AM | 09/01/17 03:03 PM | 09/01/17 03:03 PM | 1 | MOD-354 | Azure Capability Provider | 0|hzzzzr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-352 | Azure Java SDK beta3 upgrade |
Task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 04/01/17 06:52 AM | 04/01/17 06:59 AM | 04/01/17 06:59 AM | 0 | Azure Capability Provider | 0|i02xbr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-330 | MOD-328 Update to newest version of VIJava |
Sub-task | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 23/12/16 08:28 AM | 03/02/17 09:32 AM | 03/02/17 09:29 AM | Capability Providers | 28/02/17 | 2 | Try the newest version of VIJava. It should support 6.x and possibly 7.x | 0|i02va7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-321 | Provide method for printing EObjects in XMI format outside 'com.virtunomic.model.vml' bundle |
Story | Backlog | Medium | Unresolved | Derek Palma | Michal Siemaszko | Michal Siemaszko | 22/12/16 12:19 PM | 22/12/16 12:19 PM | 0 | Currently, `com.virtunomic.model.runtime.VmlEObjectUtil.dumpXMI(EObject)` method cannot be used from bundles which are required by 'com.virtunomic.model.vml' bundle, causing cycle error (e.g. 'com.virtunomic.microsoft.azure.client' bundle) | 0|i02v3r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-318 | Build EMF model for all resources in a given resource group |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/12/16 03:15 PM | 22/12/16 03:10 PM | 22/12/16 03:10 PM | 0 | Azure Capability Provider | 0|i02ugf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-309 | Enable Azure Resource Manager (ARM) VNET Gateway Diagnostic Logs |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/12/16 12:50 PM | 09/01/17 10:23 AM | 0 | MOD-268 | Azure Capability Provider | 0|i02to7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-297 | Azure QA test suite - prepare necessary tests |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 10/12/16 08:08 AM | 21/12/16 09:35 AM | 3 | Azure Capability Provider | 0|i02srb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-295 | Show format activity log entry for each formatted disk |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 09/12/16 01:06 PM | 07/01/17 10:58 AM | 07/01/17 10:58 AM | Capability Providers | 0 | Azure_MOD-295_display.png | Currently all disks fall under a single activity. | Azure Capability Provider | 0|i02sj3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-286 | ASA Client |
Story | In Progress | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 08/12/16 08:12 AM | 29/06/17 06:24 AM | 26/06/17 12:56 PM | Capability Providers | 0 | MOD-285 | Create an ASA client for the ASA REST API. | Cisco ASA support | 0|i0001a:i60000001cd | NTP Service 1 Tier | CTL Lab Readiness-April, CTL Lab Readiness-May, CTL Lab Readiness-June | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-276 | Determine the number of cores in use in a subscription |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 07/12/16 06:00 PM | 13/12/16 11:12 AM | 13/12/16 11:12 AM | Capability Providers | 0 | We need to programmatically determine the following core information per subscription:
1. Total cores 2. Cores in use 3. Cores available Only 2 of the above values are required to compute the 3rd. |
Azure Capability Provider | 0|i02r8n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-274 | Retrieve resources by ID |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/12/16 06:00 AM | 22/12/16 03:09 PM | 22/12/16 03:09 PM | 1 | Ability to retrieve by ID resources of type:
- "Microsoft.Storage/storageAccounts" - "Microsoft.Compute/availabilitySets" - "Microsoft.Network/connections" - "Microsoft.Network/publicIPAddresses" - "Microsoft.Network/virtualNetworks" - "Microsoft.Network/virtualNetworks/virtualNetworkPeerings" - "Microsoft.Network/virtualNetworkGateways" - "Microsoft.Network/networkInterfaces" - "Microsoft.Network/networkSecurityGroups" - "Microsoft.Compute/virtualMachines" - "Microsoft.Compute/virtualMachines/extensions" |
Azure Capability Provider | 0|i02pyn: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-271 | Tracking status of active Azure resources |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 29/11/16 07:55 PM | 09/01/17 10:29 AM | Capability Providers | 0 | Check if there is a way to detect the status of active Azure resources in an event driven manner. (By active resources I mean VMs, gateways vs passive resources like public IPs and availability sets)
|
Azure Capability Provider | 0|i02nav: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-270 | Azure alerts |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 28/11/16 08:48 PM | 09/01/17 10:27 AM | Capability Providers | 0 | Alerts seem to be supported for metric, activity logs and log analysis.
Create alerts programmatically for each of these cases. What kinds of notifications are supported? They mention email. What about SMS etc. Is there metadata or APIs for discovering these? |
Azure Capability Provider | 0|i02n3r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-269 | Azure acvtivity logs for specific resources |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 28/11/16 08:42 PM | 09/01/17 10:28 AM | Capability Providers | 0 | Programmatically obtain the activity logs available for each resource.
Query for logs for a resource. Create an email or webhook alert that triggers off an Activity Log event. Determine what kind of archiving of logs is supported. Can retention be controlled? |
Azure Capability Provider | 0|i02n3j: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-268 | Azure diagnostics logs |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 28/11/16 08:39 PM | 09/01/17 10:27 AM | Capability Providers | 0 | MOD-309 | Programmatically obtain the diagnostics logs available for each resource.
Query for logs for a resource. Set alerts. Determine the kinds of alerts supported. Determine what kind of archiving of logs is supported. Can retention be controlled? See how OMS analytics and be configured and used. |
Azure Capability Provider | 0|i02n3b: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-259 | Azure monitoring metrics |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 24/11/16 10:10 PM | 09/01/17 10:26 AM | Capability Providers | 0 | Programmatically obtain the metrics available for each resource. This is represented as some kind of schema.
Query for metrics for a resource. Set thresholds on a metrics to generate alerts. Determine the kinds of alerts supported. Determine what kind of archiving of metrics is supported. Can retention be controlled? |
Azure Capability Provider | 0|i02lbr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-258 | AzureClient methods should only throw IOException |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 19/11/16 10:04 AM | 21/11/16 12:02 PM | 21/11/16 12:02 PM | Capability Providers | 0 | All methods that call into the Azure API should throw IOException (not Exception or a subclass of IOException) and no other Exceptions. This allows the calling layer to deal with clients in uniform manner and to know when it needs to deal with IO/Transport issues.
There can be exceptions to this rule, like if the method does some computation and does not interact with an API endpoint, but these are rare. |
Azure Capability Provider | 0|i025yf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-257 | AzureClient support for programming Azure Security center |
Story | Stopped working | Low | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 19/11/16 09:21 AM | 09/01/17 10:25 AM | 0 | Azure Security Center is a service which Vnomic needs to be able to control. It is not controllable via ARM templates, so an API approach must be used.
Investigate what APIs are available. It is important to be able to control the policy configuration. If enough APIs are available, create a test to enable for a subscription and and set some policies. Check with Derek before doing this because we don't want to use our main subscription. |
Azure Capability Provider | 0|i025rz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-256 | AzureClient support for creating and deleting resource locks |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 19/11/16 08:48 AM | 01/12/16 06:56 AM | 01/12/16 06:56 AM | Capability Providers | 2 | MOD-247 | Subscriptions, ResourceGroups and all resources in a ResourceGroup can be locked. Add support to the AzureClient to create/delete locks.
Test/verify the following cases: 1. With same Vnomic client service principal, create a lock and delete a resources on resources created in a deployment using the same service principal. Make sure the delete method reports the existing of the lock preventing the deletion clearly (since we expect this to happen in practice). 2. Create a lock using a different service principal (simulating a customer's unique one) which will cause the Vnomic service principal to fail to delete the lock due to lack of permissions. This is the case where Vnomic creates some resources, then the customer uses his identity+permissions to lock the resource which prevents Vnomic from being able to programmatically delete the resource using its client service principal. The ensures the customer can lock resources and prevent Vnomic from destroying them. |
Azure Capability Provider | 0|i025mv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-255 | Ensure common identity across all Azure APIs |
Story | Stopped working | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 19/11/16 08:16 AM | 05/01/17 01:19 PM | 05/12/16 10:55 AM | Capability Providers | 4 | MOD-254 | The AzureClient class currently uses the Azure Resource Management API. We need to use the Azure Service Management API and have integrated this to the AzureClient. These APIs receive authentication differently. We need to ensure the following:
1. All APIs are invoked using the same identity (service principal). 2. Check that this is true by writing a test to read back the appropriate identify information. This should be done for each management API added to the AzureClient. 3. This test needs to be run as part of the normal CI tests manged by Alexandru and Radek. I.e. we want these test run for each new build. |
Azure Capability Provider | 0|i025hr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-254 | Azure Service Management API Authentication |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 18/11/16 09:18 AM | 05/12/16 10:56 AM | 05/12/16 10:56 AM | 0 | MOD-255 | Most operations run against Azure API so far are authenticated using access token, running against Azure Resource Management API.
For Azure Service Management API, authentication is not handled the same. Determine best way to programmatically authenticate against Azure Service Management API and integrate this method into existing ASM methods in AzureClient. |
Azure Capability Provider | 0|i0205z: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-253 | MOD-243 http_redirect_class data group |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 16/11/16 07:16 AM | 21/11/16 09:37 AM | 21/11/16 09:37 AM | 0 | 0|i01u4n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-252 | MOD-243 http_redirect iRule |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 16/11/16 07:16 AM | 21/11/16 09:37 AM | 21/11/16 09:37 AM | 0 | 0|i01u4f: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-251 | Programmatically query VM images from Azure |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 15/11/16 10:37 AM | 05/12/16 10:47 AM | Capability Providers | 0 | Programmatically query Azure VM images by publisher, offer, SKU, and/or version (there may be other attributes to filter by but lest start with these.
|
Azure Capability Provider | 0|i01psf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-250 | Programmatically obtain Azure VM sizes |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 15/11/16 10:34 AM | 05/12/16 10:46 AM | Capability Providers | 0 | Unlike VMWare VMs where we can set the memory size and number of cores to a value we want, clouds like Azure just provide a number of VMs with specific configurations. Azure calls these VM sizes. In our development code we have expressions like:
vm.setVmSize(InternalConstants.AZURE_MINIMAL ? "Standard_A3" : "Standard_A7"); This just sets the VM size using no information about the VM size. We need to obtain descriptive information about all the VM sizes available so our resource selection algorithms can select the right VM size based on the tier resource requirements. The objective of this task is to obtain this information via the Azure APIs. |
Azure Capability Provider | 0|i01prr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-249 | Determine how to use NetworkManagementClientImpl.newInstance in Azure JAVA SDK |
Story | Done | High | Done | Michal Siemaszko | Derek Palma | Derek Palma | 14/11/16 08:46 AM | 18/11/16 09:25 AM | 18/11/16 09:25 AM | Capability Providers | 0 | The Azure JAVA SDK has: com.microsoft.windowsazure.management.network.NetworkManagementClientImpl.newInstance(HttpClientBuilder, ExecutorService)
This seems to provide the needed granular access for all network objects. However, it is not clear how to use this interface via the Azure object we have in the AzureClient. Perhaps there is some specialized way to get an instance to this interface. The AzureClient should be enhanced to provide an instance of this interface. Also, I presume they'd be using this pattern for other kinds of resources too. The following looks like a relevant example but needs to be tried: http://www.programcreek.com/java-api-examples/index.php?source_dir=azure-sdk-for-java-master/azure-mgmt-samples/src/main/java/com/microsoft/azure/samples/compute/CreateVirtualNetworkExample.java |
Azure Capability Provider | 0|i01jnr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-248 | Attach Azure Java SDK Source |
Story | Done | High | Done | Michal Siemaszko | Derek Palma | Derek Palma | 14/11/16 08:09 AM | 14/11/16 08:14 AM | 14/11/16 08:14 AM | Capability Providers | 0 | Make the Azure JAVA SDK source available from our dev IDE so we can inspect/browse the source code. | Azure Capability Provider | 0|i01jhj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-247 | Support creating resource locks for ResourceGroups and Subscriptions |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 09/11/16 07:52 AM | 26/11/16 01:17 PM | 26/11/16 01:17 PM | Capability Providers | 0 | MOD-256 | It's clear how to set locks on resources in a ResourceGroup and how to do this in a template (see this example: https://azure.microsoft.com/en-us/documentation/articles/resource-group-lock-resources/) However, ResourceGroups and Subscriptions don't seem to be accessible from templates (they are actually the containers of resources). And we currently create ResourceGroups manually to deploy templates into.
Investigate how locks can be set and removed for ResourceGroups and Subscriptions. If this is not doable with the JAVA SDK it should be possible from the REST API since there are powershell examples (see: https://msdn.microsoft.com/en-us/library/mt652515.aspx). |
Azure Capability Provider | 0|i01auf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-246 | MOD-243 Create a unique self signed key and certificate for RP Inside per-application iApp |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/11/16 09:39 AM | 21/11/16 09:37 AM | 21/11/16 09:37 AM | 0 | 0|i01anz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-245 | MOD-243 Create a Static route on RP Inside vCMP Guest |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/11/16 09:38 AM | 16/11/16 07:14 AM | 16/11/16 07:14 AM | 0 | 0|i01anr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-244 | MOD-243 Replace Service Routing iRule for RP Outside main iApp with older version |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/11/16 09:34 AM | 16/11/16 07:14 AM | 16/11/16 07:14 AM | 0 | 0|i01anj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-243 | F5 client - Release #2, Batch #3 |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/11/16 04:04 AM | 08/12/16 01:08 PM | 08/12/16 01:08 PM | 1 | MOD-244, MOD-245, MOD-246, MOD-252, MOD-253 | Load Balancing Capability Provider | 0|i01ahb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-242 | MOD-220 Test/debug HA VCMP implementation |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 01/11/16 08:17 AM | 08/12/16 09:44 AM | 08/12/16 09:44 AM | 0 | 0|i019k7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-241 | Research API to compute costs of Azure resources |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 01/11/16 07:43 AM | 02/12/16 08:59 AM | 02/12/16 08:59 AM | 0 | We need a way to compute costs of resources before and after they are provisioned on Azure.
Google: azure ratecard api 1. Determine how to compute the cost of all resources in a resource group on Azure. 2. Determine how we can compute the cost of resources before we provision them on Azure. Computation before will require the ability to select resources (Vnomic will have to know about these) and have cost metadata associated with them so the fulfillment operation can optimize cost. Don't worry about the Vnomic model, focus on getting the metadata that would enable this, i.e. the APIs to get metdata for VMs and storage, for example. |
Azure Capability Provider | 0|i019jz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-240 | Obtain resource Ids for each deployed Azure resource |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 01/11/16 07:15 AM | 04/11/16 10:39 AM | 04/11/16 10:39 AM | Capability Providers | 0 | For each resource created using an ARM template, we must compute or obtain the resource ID so this value can be added to the RPM entities representing the resource to allow direct mapping between the Vnomic resource model and resources in Azure.
The resourecId should match what Azure calls a resource ID. See: https://azure.microsoft.com/en-us/documentation/articles/resource-group-overview/ https://azure.microsoft.com/en-us/documentation/articles/resource-group-authoring-templates/#resources |
Azure Capability Provider | 0|i019jr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-238 | MOD-220 Test/debug HA VE implementation |
Sub-task | Stopped working | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 26/10/16 09:13 AM | 01/11/16 08:17 AM | 31/10/16 10:58 AM | 0 | 0|i018xb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-237 | VE HA support |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 26/10/16 05:59 AM | 31/10/16 10:58 AM | 31/10/16 10:58 AM | Capability Providers | 0 | In trying to use the VCMP code to configure VE HA it fails with error:
com.virtunomic.f5.icontrol.client.F5ClientException: Request unsuccessfull! HTTP code returned '404', reason 'Not Found' 01020036:3: The requested Re-Key (system device) was not found. com.virtunomic.f5.icontrol.client.F5ClientException Request unsuccessfull! HTTP code returned '404', reason 'Not Found' 01020036:3: The requested Re-Key (system device) was not found. atcom.virtunomic.f5.icontrol.common.F5Utils.handleError(F5Utils.java:20)[na:na] atcom.virtunomic.f5.icontrol.service.AbstractF5IControlService.validateResponse(AbstractF5IControlService.java:188)[na:na] atcom.virtunomic.f5.icontrol.service.AbstractF5IControlService.executeRequest(AbstractF5IControlService.java:322)[na:na] atcom.virtunomic.f5.icontrol.service.BigIpConfigurationService.configureName(BigIpConfigurationService.java:247)[na:na] atcom.virtunomic.f5.icontrol.client.F5BigIpClient.configureName(F5BigIpClient.java:811)[com.virtunomic.f5:1.0.0.qualifier] atcom.virtunomic.model.content.packager.VMwareVSphereSupport.provisionVirtualMachine(VMwareVSphereSupport.java:672)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor.doExecuteUpdateOperation(UpdatePlanExecutor.java:462)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor.access$1(UpdatePlanExecutor.java:393)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor$3.run(UpdatePlanExecutor.java:386)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdateProgressMonitor.executeMonitoredUpdateOperation(UpdateProgressMonitor.java:178)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdateOperation(UpdatePlanExecutor.java:390)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdateOperations(UpdatePlanExecutor.java:314)[com.virtunomic.model.vml:1.0.0.qualifier] atcom.virtunomic.model.content.packager.UpdatePlanExecutor.executeUpdate(UpdatePlanExecutor.java:230)[com.virtunomic.model.vml:1.0.0.qualifier] |
Load Balancing Capability Provider | 0|i018x3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-236 | MOD-220 Update 'RP_OutsideLoadBalancer' and 'RP_InsideLoadBalancer' classes |
Sub-task | Done | Medium | Done | Derek Palma | Michal Siemaszko | Michal Siemaszko | 24/10/16 12:33 PM | 07/12/16 07:21 PM | 07/12/16 07:21 PM | 0 | See #deleteInsideLoadBalancerResources and #deleteOutsideLoadBalancerResources in 'com.virtunomic.model.content.packager.F5VCMPSupport' on 'br_F5_stabilize3' branch what additional data is needed in 'Resource_OutsideLBSpec' and 'Resource_InsideLBSpec', what is obsolete, i.e.:
1. In 'RP_InsideLoadBalancer' class (passed to #deleteInsideLoadBalancerResources method in 'F5VCMPSupport') a) needs additional fields/getters: #getHttpsIAppName() String #hasHttpIApp() boolean #getHttpIAppName() String b) does not need anymore: #getHttpVsName() String 2. In 'RP_OutsideLoadBalancer' class (passed to #deleteOutsideLoadBalancerResources method in 'F5VCMPSupport') a) needs additional fields/getters: #getDataGroupHttpPoolRecordName() String #getDataGroupHttpsPoolRecordName() String #getHttpPoolIAppName() String #getHttpsPoolIAppName() String b) does not need anymore: #getDataGroupRecordName() String |
0|i018wf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-235 | MOD-220 Update 'Resource_OutsideLBSpec' and 'Resource_InsideLBSpec' classes |
Sub-task | Done | Medium | Done | Derek Palma | Michal Siemaszko | Michal Siemaszko | 24/10/16 12:33 PM | 07/12/16 07:21 PM | 07/12/16 07:21 PM | 0 | MOD-219 | See #provisionOutsideLB and #provisionInsideLB in 'com.virtunomic.model.content.packager.F5VCMPSupport' on 'br_F5_stabilize3' branch what additional data is needed in 'Resource_OutsideLBSpec' and 'Resource_InsideLBSpec', what is obsolete, etc.
|
0|i018w7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-234 | MOD-220 Test/debug v2.0 implementation |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/10/16 04:55 AM | 25/10/16 01:53 PM | 25/10/16 01:53 PM | 0 | 0|i018v3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-233 | MOD-220 Update 'InsideRpConfig' (rename to 'InsideRpPerAppConfig'?), 'OutsideRpPerAppConfig' - add missing params, setters & getters, remove obsolete, compile list of params to be passed when populating these objects in F5VCMPSupport |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/10/16 04:55 AM | 24/10/16 08:55 AM | 24/10/16 08:55 AM | 0 | 0|i018uv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-232 | MOD-220 Deprovisioning/cleanup of per application LB configuration - review and implement missing methods if needed, update deprovisioning/cleanup in F5VCMPSupport |
Sub-task | Stopped working | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/10/16 04:54 AM | 31/10/16 11:28 AM | 25/10/16 01:53 PM | 0 | 0|i018un: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-231 | MOD-220 Update data group for both 80, 443 - implement |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/10/16 04:53 AM | 24/10/16 08:31 AM | 24/10/16 08:31 AM | 0 | 0|i018uf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-230 | MOD-220 Move new & old constants to F5Constants, remove obsolete |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 24/10/16 04:53 AM | 24/10/16 08:48 AM | 24/10/16 08:48 AM | 0 | 0|i018u7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-228 | MOD-220 Remove obsolete sequence steps for Outside and Inside VCMP Guests |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:06 AM | 19/10/16 01:36 PM | 19/10/16 01:36 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "B. Configure common Service Routing on the Outside VCMP Guest" -> "8. Push One-Connect Profile for Service Routing Virtual Server on Outside vCMP Guest (HTTPS & HTTP)" (page 16)
REMOVED existing one-connect profile creation step * added just recently (last week), in release #2 batch #1 set of tasks @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "II. Per application inside sequence for Apps" -> "C. Configure HTTPS Virtual Server on the Inside VCMP Guest" -> Push One-Connect Profile for Service Routing Virtual Server on Inside vCMP Guest (HTTPS & HTTP)" (page 69) REMOVED existing one-connect profile creation step * added just recently (last week), in release #2 batch #1 set of tasks @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "10. Disable pool that's created w/ iApp on vCMP guest" (page 31) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "11. Delete pool that's created w/ iApp on vCMP guest" (page 31) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "D. Configure Service Routing for HTTP (port 80) on the Outside vCMP Guest" -> "11. Disable pool that's created w/ iApp on vCMP guest" (page 46) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "D. Configure Service Routing for HTTP (port 80) on the Outside vCMP Guest" -> "12. Delete pool that's created w/ iApp on vCMP guest" (page 46) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "1. Create pool on vCMP guest" (page 47) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "2. Assign member to pool on port 443 on vCMP guest" (page 47) REMOVED existing step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "3. Assign member to pool on port 80 on vCMP guest" (page 47) REMOVED existing step in sequence @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "II. Per application inside sequence for Apps" -> "C. Configure HTTPS Virtual Server on the Inside VCMP Guest" -> "10. Assign member to internal pool for port 443" (page 84) REMOVED existing step in sequence @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "II. Per application inside sequence for Apps" -> "D. Configure HTTP Virtual Server on the Inside VCMP Guest" -> "11. Assign member to internal pool for port 80" (page 87) REMOVED existing step in sequence |
0|i018i7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-227 | MOD-220 Outside VCMP Guest iRule definition update |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:06 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "B. Configure common Service Routing on the Outside VCMP Guest" -> "7. Create an iRule on vCMP guest" (page 15-16)
MODIFIED existing step in sequence * different iRule used |
0|i018hz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-226 | MOD-220 WAF for Fabric Layer (Basic and upload framework) |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:05 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "6. Provision the ASM on the inside vCMP Guest" (page 70)
ADDED new step in sequence * affects how code in F5VCMPSupport is structured - must be run in 'main'/'run once' sequence for inside RP @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "7. Push the ASM DDoS Policy on the Inside vCMP Guest" (page 70-71) ADDED new step in sequence * affects how code in F5VCMPSupport is structured - must be run in 'main'/'run once' sequence for inside RP * corresponds to item #21 "WAF for Fabric Layer (Basic and upload framework)" from "Spec Batch 2 Release" in 'Release 2 Spec Batch Release Schedule.docx' document |
0|i018hr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-225 | MOD-220 Refactor of F5VCMPSupport code to allow for common service routing configuration |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:05 AM | 19/10/16 01:36 PM | 19/10/16 01:36 PM | 0 | @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "8. Ensure SSH is available on vCMP guest"
MOVED to 'main'/'run once' sequence - * run before template is uploaded, which should be done only once @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "9. Copy & load the 'appsvcs_integration_v2.0_001_sap' iApp template on the vCMP guest" MOVED to this 'main'/'run once' sequence * template should be uploaded only once @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "6. Provision the ASM on the inside vCMP Guest" (page 70) ADDED new step in sequence * affects how code in F5VCMPSupport is structured - must be run in 'main'/'run once' sequence for inside RP @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "I. Main inside sequence" -> "B. Configure common Service Routing on the Inside VCMP Guest" -> "7. Push the ASM DDoS Policy on the Inside vCMP Guest" (page 70-71) ADDED new step in sequence * affects how code in F5VCMPSupport is structured - must be run in 'main'/'run once' sequence for inside RP |
0|i018hj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-224 | MOD-220 Web Socket Support |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:05 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "10. Push Web Socket Profile on the Outer vCMP Guest" (page 18)
ADDED new step in sequence * corresponds to item #18 "Web Socket Support" from "Spec Batch 2 Release" in 'Release 2 Spec Batch Release Schedule.docx' document |
0|i018hb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-223 | MOD-220 DDoS for Access Layer |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:04 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "8. Provision AFM Firewall on the Outer vCMP Guest" (page 17)
ADDED new step in sequence @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "9. Push AFM Policy on the Outer vCMP Guest for DDoS" (page 17-18) ADDED new step in sequence * corresponds to item #20 "DDoS for Access Layer" from "Spec Batch 2 Release" in 'Release 2 Spec Batch Release Schedule.docx' document |
0|i018h3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-222 | MOD-220 Configuration and creation of application pools |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:04 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "1. Update data group on vCMP guest" (page 47)
MODIFIED existing step in sequence * run for HTTP iApp (step #2 below) @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "2. Deploy Application Pool rp1 on Outside vCMP Guest for http using iApps" (page 48-57) ADDED new step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "3. Update vCMP Guest Data-Group entry for HttpS Application" (page 57) MODIFIED existing step in sequence * run for HTTPS iApp (step #4 below) @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "II. Per application outside sequence for Apps" -> "4. Deploy Application Pool rp2 on Outside vCMP Guest for httpS using iApps" (page 57-66) ADDED new step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different |
0|i018gv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-221 | MOD-220 Refactor of iApp configuration and creation code to allow for new payload format and URL used with 'appsvcs_integration_v2.0_001_sap' template |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 13/10/16 10:03 AM | 19/10/16 01:35 PM | 19/10/16 01:35 PM | 0 | @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "C. Configure Service Routing for HTTPS (port 443) on the Outside VCMP Guest" -> "11. Create HTTPS iApp with iRule attached on vCMP guest" (page 19-31)
MODIFIED existing step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different * as part of this update/modification, work done as part tasks in release #2 batch #1 is being removed @ "Overview sequence steps for DNS, Service Routing & Reverse Proxy on the Outside vCMP Guest" -> "I. Main sequence" -> "D. Configure Service Routing for HTTP (port 80) on the Outside vCMP Guest" -> "10. Create HTTP Virtual Server on vCMP guest using iApps" (page 31-46) MODIFIED existing step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different * as part of this update/modification, work done as part tasks in release #2 batch #1 is being removed @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "II. Per application inside sequence for Apps" -> "C. Configure HTTPS Virtual Server on the Inside VCMP Guest" -> "9. Create HTTPS Virtual Server with pool via iApp" (page 72-84) MODIFIED existing step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different * as part of this update/modification, work done as part tasks in release #2 batch #1 is being removed @ "Overview sequence steps for Service Routing & Reverse Proxy on the Inside vCMP Guest" -> "II. Per application inside sequence for Apps" -> "D. Configure HTTP Virtual Server on the Inside VCMP Guest" -> "10. Create HTTP Virtual Server using iApp" (page 85-99) MODIFIED existing step in sequence * template - new (appsvcs_integration_v2.0_001_sap) * payload - completely different way of how iApp payload is being constructed * path - different * as part of this update/modification, work done as part tasks in release #2 batch #1 is being removed |
0|i018gn: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-220 | F5 client - Release #2, Batch #2 |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/10/16 06:55 AM | 08/12/16 09:44 AM | 08/12/16 09:44 AM | 1 | MOD-221, MOD-222, MOD-223, MOD-224, MOD-225, MOD-226, MOD-227, MOD-228, MOD-230, MOD-231, MOD-232, MOD-233, MOD-234, MOD-235, MOD-236, MOD-238, MOD-242 | Features selected for release #2, batch #2 | Load Balancing Capability Provider | 0|i0184n: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-219 | Additional fields needed in 'Resource_InsideLBSpec' |
Story | Done | Medium | Done | Derek Palma | Michal Siemaszko | Michal Siemaszko | 07/10/16 12:13 PM | 08/12/16 09:39 AM | 08/12/16 09:39 AM | 0 | MOD-206, MOD-207, MOD-208, MOD-209, MOD-210, MOD-211, MOD-213, MOD-216, MOD-235 | Additional attributes needed in 'Resource_InsideLBSpec'
In per-application reverse proxy inside sequence - since OneConnect profile for both HTTPS and HTTP is introduced and HTTP Service Routing is created via iApp now - configuration passed in 'InsideRpConfig' needs additional data to be present in 'Resource_InsideLBSpec'. 'com.virtunomic.model.f5.Resource_InsideLBSpec' class needs following additional attributes: * httpIAppName (InsideRpConfig#setHttpIAppName) * httpIAppDescription (InsideRpConfig#setHttpIAppDescription) * httpIAppVsName (InsideRpConfig#setHttpIAppVsName) * httpsOneConnectProfile (InsideRpConfig#setHttpsOneConnectProfile) * httpOneConnectProfile (InsideRpConfig#setHttpOneConnectProfile) |
Load Balancing Capability Provider | 0|i017kf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-217 | MOD-205 Store API version information for version specific logic and resource use |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 10:05 AM | 03/10/16 01:12 PM | 03/10/16 01:11 PM | 1 | Logic in API calls/sequences and resources used (e.g. Access Policy) varies depending on which version of BIGIP API is being used (e.g. 11.x or 12.x). Retrieve this information when establishing connection to BIGIP and store and use internally in client. | 0|i017gv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-216 | MOD-205 Create HTTP virtual Servers using iApps |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:35 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #12 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017g7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-215 | MOD-205 Remove the extra Virtual server for the application |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:35 AM | 07/10/16 12:14 PM | 07/10/16 12:14 PM | 0 | Corresponds to item #11 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017fz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-213 | MOD-205 TCP Optimizations |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:33 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #9 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017fj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-212 | MOD-205 Dynamically Determine Viprion Blade cores using APIs |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:31 AM | 06/10/16 10:06 AM | 06/10/16 10:06 AM | 06/10/16 | 1 | MOD-161 | Corresponds to item #8 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017fb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-211 | MOD-205 Virtual Server: x-forwarded-for header |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:31 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #7 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017f3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-210 | MOD-205 HTTP Resource Persistance, default-Cookie, fallback-Server Address (Fabric Layer) |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:31 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #6 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017ev: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-209 | MOD-205 Protocol Profile client and server (Access & Fabric) |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:30 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #5 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017en: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-208 | MOD-205 Custom OneConnect Profile (Access & Fabric Layer) |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:30 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 06/10/16 | 0 | MOD-219 | Corresponds to item #4 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017ef: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-207 | MOD-205 Disable SNAT on Service Routing Virtual Server |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:30 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 0 | MOD-219 | Corresponds to item #3 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017e7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-206 | MOD-205 Update monitors for the virtual servers |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:29 AM | 24/10/16 12:35 PM | 24/10/16 12:35 PM | 06/10/16 | 0 | MOD-219 | Corresponds to item #2 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017dz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-205 | F5 client - Release #2, Batch #1 |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:27 AM | 07/11/16 04:10 AM | 07/11/16 04:10 AM | 1 | MOD-206, MOD-207, MOD-208, MOD-209, MOD-210, MOD-211, MOD-212, MOD-213, MOD-215, MOD-216, MOD-217 | Features selected for release #2, batch #1
|
Load Balancing Capability Provider | 0|i017dr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-201 | Azure client error reporting |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 02/10/16 08:03 PM | 15/11/16 01:31 PM | 15/11/16 01:31 PM | Capability Providers | 0 | 1. Determine how errors are reported via the API. For example, does the returned exception object contain all the information, or does the Azure activity log or some other thing need to be queried.
2. Ensure complete error information appears in the Vnomic activity log. If necessary create specialized objects to hold the information. 3. Work with Derek to identify a few error cases that can be used to explore this issue. |
Azure Capability Provider | 0|i017br: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-200 | Support cancellable wait in Azure client operations |
Story | Done | Medium | Done | Michal Siemaszko | Derek Palma | Derek Palma | 02/10/16 07:56 PM | 15/11/16 01:32 PM | 15/11/16 01:32 PM | Capability Providers | 0 | Use the Azure client API async approach to let the caller thread support cancellable wait. | Azure Capability Provider | 0|i017bj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-196 | ARM template deployment |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 15/09/16 09:26 AM | 02/10/16 07:54 PM | 02/10/16 07:54 PM | 0 | Azure Capability Provider | 0|i016on: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-195 | CRUD for resource groups |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 15/09/16 09:26 AM | 07/11/16 06:00 AM | 07/11/16 06:00 AM | 0 | Azure Capability Provider | 0|i016of: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-194 | OSGify Azure Java SDK |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 15/09/16 09:24 AM | 16/09/16 03:47 PM | 16/09/16 03:47 PM | 15/09/16 | 0 | Create bundle named com.virtunomic.microsoft.azure.client, OSGi wrapper for Azure Java SDK JARs and dependencies.
Do not implement any custom class hierarchy yet - implementation done as a unit test, directly calling Azure Java SDK classes. Using existing ARM templates from GitHub / static JSON where possible. |
Azure Capability Provider | 0|i016o7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-193 | Azure Capability Provider |
Epic | In Progress | Medium | Unresolved | Derek Palma | Michal Siemaszko | Michal Siemaszko | 15/09/16 07:53 AM | 12/02/17 05:15 PM | Capability Providers | 1 | MOD-197 | ghx-label-1 | Azure Capability Provider | To Do | 0|i016nr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-188 | MOD-68 F5 - Synching F5 sequence documentation with implementation |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 21/08/16 07:36 AM | 29/08/16 08:25 AM | 29/08/16 08:25 AM | 1 | ACI | 0|i00tbj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-184 | Consul Catalog Http Endpoint Client |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/08/16 09:04 AM | 15/08/16 07:11 AM | 15/08/16 07:11 AM | 0 | Implement Java client for Consul's Catalog HTTP Endpoint (https://www.consul.io/docs/agent/http/catalog.html) | ACI | Service discovery capability provider | 0|i00jxr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-183 | Service discovery capability provider |
Epic | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 12/08/16 09:03 AM | 15/08/16 06:30 AM | 0 | ACI | ghx-label-2 | Service discovery capability provider | To Do | 0|i00jxj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-179 | MOD-68 F5 - Resources' naming changes |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 08/08/16 06:01 AM | 09/08/16 12:28 PM | 09/08/16 12:28 PM | 09/08/16 | 0 | Modify resources' naming as per attached PPT. | ACI | 0|i00hyv: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-176 | MOD-68 F5 - HA - improvements and missing functionality |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/08/16 07:57 AM | 12/08/16 09:19 AM | 12/08/16 09:19 AM | 12/08/16 | 0 | Improvements for:
- com.virtunomic.f5.icontrol.client.F5BigIpSoapClient.haAddDeviceGroupDevices(String, String[]) - com.virtunomic.f5.icontrol.client.F5BigIpSoapClient.haDevicesInSync(String) Missing functionality: - "checking if peer exists" - "checking if sync failover group exists" - "checking for active/standby mode" / "whether current node is active" - "switching between active/standby" - "resetting / removing devices from sync failover group and group itself" |
ACI | 0|i00ctb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-175 | MOD-68 F5 - VCMP - Deletion support for per-application inside/outside RP sequences |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 01/08/16 08:09 AM | 02/08/16 02:40 PM | 02/08/16 02:40 PM | 0 | ACI | 0|i00chr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-174 | MOD-68 F5 - Service Routing documentation - merge snippets and outline based on implementation with "original" Service Routing document |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 26/07/16 10:13 AM | 26/07/16 10:14 AM | 26/07/16 10:14 AM | 1 | ACI | 0|i00a7b: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-171 | MOD-68 F5 - Failing operations - collect details about errors/exceptions that happen and provide them to F5 |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/07/16 10:10 AM | 21/08/16 07:19 AM | 21/08/16 07:19 AM | 0 | ACI | 0|i00a1r: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-165 | MOD-68 F5 - VCMP - undeploy - add checks/retries to verify resources are removed |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:28 PM | 02/08/16 02:40 PM | 02/08/16 02:40 PM | 02/08/16 | 0 | ACI | 0|i009sf: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-164 | MOD-68 F5 - Connection check and delays - ability to enable/disable, specify delay w/ connection check |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:28 PM | 25/07/16 02:05 PM | 25/07/16 02:05 PM | 1 | ACI | 0|i009s7: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-163 | MOD-68 F5 - VCMP - add retryable for failing operations |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:28 PM | 02/08/16 02:39 PM | 02/08/16 02:39 PM | 05/08/16 | 0 | ACI | 0|i009rz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-162 | MOD-68 F5 - VCMP - High Availability - integrate and test |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:28 PM | 29/07/16 04:16 AM | 29/07/16 04:16 AM | 01/08/16 | 0 | ACI | 0|i009rr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-161 | MOD-68 F5 - VCMP - slots and cores API - implement, integrate, test |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:28 PM | 06/10/16 10:07 AM | 06/10/16 10:07 AM | 06/10/16 | 0 | MOD-212 | ACI | 0|i009rj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-160 | MOD-68 F5 - Integrate AD/LDAP client |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/07/16 01:27 PM | 02/08/16 02:38 PM | 02/08/16 02:38 PM | 03/08/16 | 0 | ACI | 0|i009rb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-145 | MOD-69 AD Client implementation v.1 |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/07/16 12:11 PM | 02/08/16 02:42 PM | 02/08/16 02:42 PM | 03/08/16 | 1 | ACI | 0|i009dj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-144 | MOD-69 AD Schema CRUD POC |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/07/16 12:10 PM | 22/07/16 10:01 AM | 22/07/16 10:01 AM | 22/07/16 | 0 | ACI | 0|i009db: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-143 | MOD-69 AD Users/Groups CRUD POC |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/07/16 12:10 PM | 20/07/16 12:11 PM | 20/07/16 12:11 PM | 0 | ACI | 0|i009d3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-120 | MOD-68 F5 Reverse Proxy functionality updates (1.5a) |
Sub-task | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 15/07/16 01:04 PM | 20/07/16 12:06 PM | 20/07/16 12:06 PM | 20/07/16 | 1 | Updates of Reverse Proxy functionality for F5 Load Balancing Capability Provider, rev. 1.5a | ACI | 0|i0087j: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-93 | Cassandra Data Storage Cluster |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/06/16 03:33 PM | 06/07/16 06:32 AM | 0 | Research available options for automating creation of Cassandra data storage clusters, implement proof of concept. | 0|i003hr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-92 | FOG Director Java client |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/06/16 02:39 PM | 07/06/16 02:39 PM | 0 | Implement FOG Director Java client | IOT Gateway Capability Provider | 0|i003hj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-91 | IOT Gateway Capability Provider |
Epic | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/06/16 02:37 PM | 07/06/16 02:39 PM | 0 | ghx-label-1 | IOT Gateway Capability Provider | To Do | 0|i003hb: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-90 | F5 ADC Capability Provider |
Epic | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/06/16 02:31 PM | 14/12/16 12:49 PM | 14/12/16 12:49 PM | 0 | Load Balancing Capability Provider | 0|i003h3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-82 | Confluent Platform Capability Provider |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 04/03/16 01:19 PM | 04/03/16 01:19 PM | 1 | Capability Provider for Confluent Platform automation. | 0|i002if: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-80 | Cluster topologies |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 22/02/16 09:28 AM | 13/07/16 07:49 AM | 1 | Research, implement POC | Hadoop Capability Provider | 0|i002cv: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-73 | GUI/Data visualization component integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 02/02/16 06:16 AM | 13/07/16 07:49 AM | 1 | Integrate selected GUI/Data visualization tool. | Hadoop Capability Provider | 0|i00287: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-72 | Data generator integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 29/01/16 01:07 PM | 13/07/16 07:50 AM | 1 | MOD-72_Data-generator-integration_tools-comparison.png | Evaluate options available for data generator component, integrate selected solution. | Hadoop Capability Provider | 0|i0027z: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-71 | Flume integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 20/01/16 11:05 AM | 13/07/16 07:50 AM | 1 | Research and integrate Apache Flume | Hadoop Capability Provider | 0|i0025z: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-70 | Nifi integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 19/01/16 10:27 AM | 13/07/16 07:50 AM | 1 | Research and integrate Apache Nifi | Hadoop Capability Provider | 0|i0025j: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-69 | Active Directory client - Release #1 |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 14/01/16 06:22 AM | 07/11/16 04:07 AM | 07/11/16 04:07 AM | 2 | MOD-143, MOD-144, MOD-145 | Implement Java client for Active Directory | Load Balancing Capability Provider | 0|i0024v: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-68 | F5 client - Release #1 |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 11/01/16 12:08 PM | 07/11/16 04:05 AM | 07/11/16 04:05 AM | 1 | MOD-120, MOD-160, MOD-161, MOD-162, MOD-163, MOD-164, MOD-165, MOD-171, MOD-174, MOD-175, MOD-176, MOD-179, MOD-188 | Implement Java client for F5 Big-IP load balancer. Features selected for release #1 | Load Balancing Capability Provider | 0|i0024n: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-67 | Storm integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/01/16 11:34 AM | 13/07/16 07:50 AM | 1 | Storm integration | Hadoop Capability Provider | 0|i0023z: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-66 | Kafka integration |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 07/01/16 11:33 AM | 13/07/16 07:50 AM | 1 | Integrate Apache Kafka | Hadoop Capability Provider | 0|i0023r: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-64 | Remote App Launcher |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 02/01/16 12:29 PM | 13/07/16 07:50 AM | 1 | Due to limitations of Oozie's Shell / SSH actions and requirement to use originally provided test apps (scala scripts, etc.) - i.e. without modifications needed to compile and package them to be run via Oozie's Spark action - a custom-made app launcher is required for remotely (SSH) launching applications on Hadoop cluster. | Hadoop Capability Provider | 0|i0022f: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-53 | HttpFS client |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 15/12/15 06:06 AM | 07/06/16 02:44 PM | 21/12/15 02:33 PM | 1 | Implement Java client for Hadoop HDFS over HTTP (HttpFS) | Hadoop Capability Provider | 0|i001yf: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-48 | Oozie client |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 23/11/15 10:02 AM | 13/07/16 07:50 AM | 1 | Implement Java client for Oozie. | Hadoop Capability Provider | 0|i001u7: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-35 | HDFS client |
Story | Done | Medium | Done | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 29/10/15 08:32 AM | 07/06/16 02:43 PM | 26/11/15 03:23 PM | 1 | Implement Java client for Hadoop Distributed File System (HDFS). | Hadoop Capability Provider | 0|i001ov: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-34 | Yarn client |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 29/10/15 08:32 AM | 13/07/16 07:50 AM | 1 | Implement Java client for Hadoop Yarn. | Hadoop Capability Provider | 0|i001on: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-30 | Investigate integration with Alien 4 Cloud |
Story | Backlog | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 23/10/15 09:15 PM | 23/10/15 09:16 PM | 1 | We want to explore integrating Alien 4 cloud with Vnomic. https://github.com/alien4cloud/alien4cloud
We need to be able to build and run this in our lab. This can be done in a Dev VM. |
0|i001nj: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Model | MOD-29 | Ambari client |
Story | Stopped working | Medium | Unresolved | Michal Siemaszko | Derek Palma | Derek Palma | 23/10/15 08:18 PM | 13/07/16 07:49 AM | Capability Providers | 1 | Implement Java client for Ambari. The REST API is defined at: https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/index.md
Create a bundle: com.virtunomic.apache.ambari.client Name the main class AmbariClient There is an Ambari client in groovy as an example: https://github.com/sequenceiq/ambari-rest-client We need our client to be in Java since Groovy adds more dependencies and complications for OSGI. We have an Hadoop cluster in the ACI lab at http://190.190.1.200:8080 which you can use for development but please don't do update operations on this server yet. We can create another one you can use and restore if you corrupt it. The read-only cluster is defined in https://vnomic.atlassian.net/browse/MOD-18 Implement CRUD operations for the following resources: Clusters Services Components Hosts Host_Components Tasks Blueprints https://cwiki.apache.org/confluence/display/AMBARI/Blueprints |
Hadoop Capability Provider | 0|i001nb: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Flexpod-Cisco | FLEX-9 | Test Automation |
Task | Done | Medium | Fixed | Michal Siemaszko | Arivalagan Kaliyaperumal | Arivalagan Kaliyaperumal | 03/07/15 01:58 AM | 21/07/15 01:58 PM | 21/07/15 01:58 PM | 2 | test jobs - run CVD commands, smoke test deployment
vnomic_bin install to test SingleNodeVApp (result of hudson build) hudson job provisions fresh SingleNodeVApp, installs vnomic_bin |
0|i0002n: | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-17 | F5 BIGIP and BIGIQ client connections must be shutdown |
Finding | Disabled | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 14/12/16 09:10 AM | 29/05/17 06:43 AM | 0 | In `com.virtunomic.model.content.packager.VMwareVSphereSupport`, all BIGIP and BIGIQ (REST) client connections are shutdown explicitly, which causes close() method to be called on `org.apache.http.impl.client.CloseableHttpClient` underneath.
In `com.virtunomic.model.content.packager.F5VCMPSupport`, BIGIP (REST) client connection is accessed via `com.virtunomic.model.state.F5Connection` and passed around between methods in this class. In order to allow for clean up of `org.apache.http.impl.client.CloseableHttpClient`, shutdown() must be called for `com.virtunomic.f5.icontrol.client.F5BigIpClient` (REST) client connection. |
0|i02tnz: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-13 | Cancellable blocking for BIG-IQ operations (registering, licensing) |
Story | Disabled | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 06/10/16 01:38 PM | 29/05/17 06:43 AM | 0 | 0|i017j3: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-12 | File Descriptor Leak Workaround (SSD) |
Story | Disabled | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/10/16 06:34 AM | 29/05/17 06:43 AM | 0 | Corresponds to item #10 from 'Release 2 Spec Batch Release Schedule.docx' document (attached) and parts of 'Service_Routing-1.8d.docx' (attached) where annotated | 0|i017fr: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-11 | F5 - SOAP endpoint connection / health check |
Story | Disabled | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 03/08/16 09:06 AM | 29/05/17 06:43 AM | 0 | ACI | 0|i00ctj: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-10 | F5 - Connection check and delays - allow for passing custom message for activity monitor |
Story | Disabled | Medium | Unresolved | Michal Siemaszko | Michal Siemaszko | Michal Siemaszko | 25/07/16 07:51 AM | 29/05/17 06:43 AM | 0 | ACI | 0|i00a13: | NTP Service 1 Tier | Restricted to agents | Restricted to agents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-3 | BIG-IP's iControl REST dameon shows incorrect information |
Finding | Disabled | Medium | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 21/03/16 01:37 PM | 29/05/17 06:43 AM | 1 | The other "Health Check" method provided by F5 - i.e. querying BigIp's REST endpoint path '/mgmt/tm/sys/service/icrd/stats' - displays incorrect information, e.g.:
a) after restarting BigIP VM, when VM was up for no longer than 5 minutes, querying https://173.36.215.221/mgmt/tm/sys/service/icrd/stats returned { "kind": "tm:sys:service:servicestats", "generation": 0, "selfLink": "https://localhost/mgmt/tm/sys/service/icrd/stats?ver=11.6.0", "apiRawValues": { "apiAnonymous": "icrd run (pid 5982) 12 minutes\n" } } b) after restarting BigIP VM again, when it was up for no longer than 3 minutes in second test, querying https://173.36.215.221/mgmt/tm/sys/service/icrd/stats returned { "kind": "tm:sys:service:servicestats", "generation": 0, "selfLink": "https://localhost/mgmt/tm/sys/service/icrd/stats?ver=11.6.0", "apiRawValues": { "apiAnonymous": "icrd run (pid 5980) 11 minutes\n" } } In both cases, process running time is shown incorrectly. This "health check" method is therefore unusable. |
0|i002nz: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-2 | BIG-IP's REST endpoint taking too long to initialize |
Finding | Disabled | High | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 21/03/16 01:36 PM | 29/05/17 06:43 AM | 1 | Every few runs, BigIp's REST endpoint fails to initialize within 5 minute timeout period currently configured and subsequent method calls will receive '503' error response ("Service Temporarily Unavailable").
Currently implemented "Health check" REST method call polls every 5 seconds '/mgmt/tm/cm/device' path and checks in response returned whether value of 'failoverState' field is 'active'. This polling however cannot wait indefinitely and times out after 5 minutes. Need BigIP's REST endpoint to initialize within this time limit at all times. |
0|i002nr: | Restricted to agents | Restricted to agents | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ADC-F5 | F5-1 | BIG-IP - BIG-IQ NTP sync up issue |
Finding | Disabled | High | Unresolved | Unassigned | Michal Siemaszko | Michal Siemaszko | 21/03/16 12:47 PM | 29/05/17 06:43 AM | 1 | Once in a while, syncing BigIP's clock with BigIQ's via NTP takes a very long time (20+ minutes). Any attempts to register ("discover") such BigIP device with BigIQ before then result in error thrown from BigIQ ("Failed to discover device because of clock skew. The clock skew between the devices is greater than 5 minutes").
The artificial delay of 10 seconds deliberately added after intial NTP configuration on BigIP via REST is not sufficient at all times. For obvious reasons, it is not possible to have it set to 20 or more minutes. Investigate cause of this sync failure, possibly implement a check (REST/SOAP method call?) whether both devices are in sync before issuing register ("discover") request to BigIQ. |
0|i002nj: | Restricted to agents | Restricted to agents |
Generated at Mon Jul 03 01:48:44 PDT 2017 by Michal Siemaszko using JIRA 1000.1092.1#100053-sha1:0458056d276544cfa37d56b1663b92738db9afcb. |