aboutsummaryrefslogtreecommitdiffstats
path: root/vid-app-common/src/test/resources/WEB-INF/jsp/welcome.jsp
blob: 1396819c73e5053316933af1bf9b480de7d1b39c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<script src="app/vid/external/multiselect/angular-bootstrap-multiselect.min.js"></script>
<div>
     <h1 class="heading1">AT&T Domain 2.0 Network</h1>
     <br>
     <h1 class="heading1"><u>Welcome to VID</u></h1>
     <br>
   The Virtual Infrastructure Deployment (VID) application allows infrastructure service deployment operators 
   to instantiate service instances and their constituent parts for Distributed service models required by the 
   internal AT&T service operations organizations that manage them, such as Mobility Network Services, 
   Netbond Services, or FlexReach Services. The models are defined by ECOMP component ASDC. The service 
   deployment operator selects the service operations owner and model that they wish to instantiate. After 
   entry of appropriate data, the operator instructs VID to direct another ECOMP component, MSO, to instantiate 
   the selected service model. Once the service instance has been instantiated, the service operator can instruct 
   VID to direct MSO to instantiate the service instance's component VNFs, VF Modules, Networks and Volume Groups. 
   The VID user can also search for, and display, existing service instances and direct the instantiation of 
   subsequent instance components.
     <br><br>
   <h1 class="heading1"><u>About VID</u></h1>
    VID was originally developed for the October 2016 release by an integrated IT and Labs team, under the 
      direction of Steve Smokowski and Vivian Pressley.
      <br><br>
    <h1 class="heading1"><a href="mailto:VID-Tier4@ist.att.com" target="_top">Contact Us</a></h1>
    <a href="mailto:VID-Tier4@ist.att.com" target="_top">Please click here to contact us.</a>

	

<BR>



</div>
<!--  Temporary solution for footer overlapping the men after talking to EComp SDK developer on 06/16/2016 -->
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>