You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by Michael Talyansky <mi...@ericsson.com> on 2017/09/05 23:07:19 UTC

Re: Initial setup for development

Hi Dave,

Thanks for the offer of help!

So far, I was able to do the following:

1. Create two VMs as recommended on the website, one for postgres and one for TrafficOps
2. Configure and start Postgres
3. Download and build Traffic Ops
4. Verify postgres connectivity and install traffic ops, according to this page: https://trafficcontrol.incubator.apache.org/docs/latest/admin/traffic_ops/installation.html
5. Brought up the GUI, downloaded and imported two missing profiles for EDGE_ATS and MID_ATS, so I have 11 profiles listed now:

Profile Name
Profile Description
Type
Cdn
Last updated
Profile Details	Parameter Details	EDGE_ATS_621_CENTOS_721	Edge Cache - Apache Traffic Server v6.2.1-61.1ec1041.el7.centos.x86_64	ATS_PROFILE	-	2017-09-05 22:54:57.061084+00
Profile Details	Parameter Details	GLOBAL	Global Traffic Ops profile, DO NOT DELETE	UNK_PROFILE	-	2017-09-05 22:14:37.180598+00
Profile Details	Parameter Details	INFLUXDB	InfluxDb profile	INFLUXDB_PROFILE	-	2017-09-05 22:14:37.194697+00
Profile Details	Parameter Details	MID_ATS_532_CENTOS_721	Mid Cache - Apache Traffic Server v5.3.2-762.23d37d0.el7.centos.x86_64	ATS_PROFILE	-	2017-09-05 22:53:35.519531+00
Profile Details	Parameter Details	RIAK_ALL	Riak profile for all CDNs	RIAK_PROFILE	-	2017-09-05 22:14:37.195611+00
Profile Details	Parameter Details	TRAFFIC_ANALYTICS	Traffic Analytics profile	UNK_PROFILE	-	2017-09-05 22:14:37.189865+00
Profile Details	Parameter Details	TRAFFIC_OPS	Traffic Ops profile	UNK_PROFILE	-	2017-09-05 22:14:37.190855+00
Profile Details	Parameter Details	TRAFFIC_OPS_DB	Traffic Ops DB profile	UNK_PROFILE	-	2017-09-05 22:14:37.191781+00
Profile Details	Parameter Details	TRAFFIC_PORTAL	Traffic Portal profile	TP_PROFILE	-	2017-09-05 22:14:37.192758+00
Profile Details	Parameter Details	TRAFFIC_ROUTER	Traffic Router profile	TR_PROFILE	-	2017-09-05 22:52:43.543589+00
Profile Details	Parameter Details	TRAFFIC_STATS	Traffic Stats profile	TS_PROFILE	-	2017-09-05 22:14:37.193739+00
Showing 1 to 11 of 11 entries


What would be the next step? Create two more VMs, download and build ATS on them? Then, where do I start configuring the whole system to be able to pass traffic?

Thanks,
Michael

On 8/31/17, 2:18 PM, "Dave Neuman" <ne...@apache.org> wrote:

    Hey Michael,
    I have built a "CDN in a box" before using KVM and a physical server but I
    haven't ever tried to build one in AWS.  I think you will need at least 3
    VMs to make this happen.  The first one should be able to run all of the TC
    components (Traffic Ops, Postgres, Traffic Monitor, Traffic Router) and you
    will need at least two caches.  We require at least a two tier CDN with at
    least one EDGE and one MID server.  It might be a little difficult getting
    all of the TC components running on one VM, but I think it can be done.
    
    Sorry, we don't really have a how-to on doing what you are trying to do,
    but I (and hopefully others) are more than happy to help here.
    
    Thanks,
    Dave
    
    On Thu, Aug 31, 2017 at 2:54 PM, Michael Talyansky <
    michael.talyansky@ericsson.com> wrote:
    
    > Hi,
    >
    > I am trying to set up development and testing environment on AWS. So far,
    > I have two VMs, one running postgres, and one on which I built
    > trafficcontrol. I will need to set up at least one caching node, so I can
    > test the whole system.
    >
    > Has anyone done something similar before, and if so, is there a pointer to
    > a sample configuration of how to do this with the least amount of VMs?
    >
    > Thanks in advance!
    >
    


Re: Initial setup for development

Posted by Michael Talyansky <mi...@ericsson.com>.
Yes, I am in, thanks!

On 9/5/17, 8:22 PM, "Mark Torluemke" <mt...@apache.org> wrote:

    Slack should be fixed now. Also, the TC admin guide has the installation
    docs: http://trafficcontrol.apache.org/docs/latest/admin/index.html
    
    On Tue, Sep 5, 2017 at 9:17 PM, Michael Talyansky <
    michael.talyansky@ericsson.com> wrote:
    
    > Thanks, Mark,
    >
    > How do I get onto Slack channel? I submitted a form a few days ago, but
    > got no reply. Just re-submitted now. Is this enough to get added?
    >
    > As far as ATS installation, is it documented as part of the Traffic
    > Control, or do I have to go to ATS page for that?
    >
    > Thanks,
    > Michael
    >
    > On 9/5/17, 7:59 PM, "Mark Torluemke" <mt...@apache.org> wrote:
    >
    >     Hi Michael,
    >
    >     If you're trying to optimize over the # of instances, I would lean away
    >     from the official production-ready recommendations in the docs, and do
    > more
    >     of what Dave suggested. Something like this:
    >
    >     +-----------+-----+
    >     | Component | VM  |
    >     +-----------+-----+
    >     | TO        | VM1 |
    >     | TODB      | VM1 |
    >     | TV        | VM1 |
    >     | TM        | VM1 |
    >     | TS        | --  |
    >     | Influx    | --  |
    >     | TR        | VM2 |
    >     | ATS-EDGE  | VM3 |
    >     | ATS-MID   | VM4 |
    >     | TP        | --  |
    >     +-----------+-----+
    >
    >     The ones with "--" can be added later, if you require that
    > functionality.
    >     Most of the components should have adequate installation
    > documentation, but
    >     reply back the list, or find us on Slack (
    > traffic-control-cdn.slack.com) if
    >     you get stuck.
    >
    >     Cheers,
    >     Mark
    >
    >
    >
    >     On Tue, Sep 5, 2017 at 5:07 PM, Michael Talyansky <
    >     michael.talyansky@ericsson.com> wrote:
    >
    >     > Hi Dave,
    >     >
    >     > Thanks for the offer of help!
    >     >
    >     > So far, I was able to do the following:
    >     >
    >     > 1. Create two VMs as recommended on the website, one for postgres
    > and one
    >     > for TrafficOps
    >     > 2. Configure and start Postgres
    >     > 3. Download and build Traffic Ops
    >     > 4. Verify postgres connectivity and install traffic ops, according
    > to this
    >     > page: https://trafficcontrol.incubator.apache.org/docs/
    >     > latest/admin/traffic_ops/installation.html
    >     > 5. Brought up the GUI, downloaded and imported two missing profiles
    > for
    >     > EDGE_ATS and MID_ATS, so I have 11 profiles listed now:
    >     >
    >     > Profile Name
    >     > Profile Description
    >     > Type
    >     > Cdn
    >     > Last updated
    >     > Profile Details Parameter Details       EDGE_ATS_621_CENTOS_721 Edge
    > Cache
    >     > - Apache Traffic Server v6.2.1-61.1ec1041.el7.centos.x86_64
    > ATS_PROFILE
    >     >    -       2017-09-05 22:54:57.061084+00
    >     > Profile Details Parameter Details       GLOBAL  Global Traffic Ops
    >     > profile, DO NOT DELETE       UNK_PROFILE     -       2017-09-05
    >     > 22:14:37.180598+00
    >     > Profile Details Parameter Details       INFLUXDB        InfluxDb
    > profile
    >     >       INFLUXDB_PROFILE        -       2017-09-05 22:14:37.194697+00
    >     > Profile Details Parameter Details       MID_ATS_532_CENTOS_721  Mid
    > Cache
    >     > - Apache Traffic Server v5.3.2-762.23d37d0.el7.centos.x86_64
    >     > ATS_PROFILE     -       2017-09-05 22:53:35.519531+00
    >     > Profile Details Parameter Details       RIAK_ALL        Riak profile
    > for
    >     > all CDNs       RIAK_PROFILE    -       2017-09-05 22:14:37.195611+00
    >     > Profile Details Parameter Details       TRAFFIC_ANALYTICS
    >  Traffic
    >     > Analytics profile       UNK_PROFILE     -       2017-09-05
    >     > 22:14:37.189865+00
    >     > Profile Details Parameter Details       TRAFFIC_OPS     Traffic Ops
    >     > profile     UNK_PROFILE     -       2017-09-05 22:14:37.190855+00
    >     > Profile Details Parameter Details       TRAFFIC_OPS_DB  Traffic Ops
    > DB
    >     > profile  UNK_PROFILE     -       2017-09-05 22:14:37.191781+00
    >     > Profile Details Parameter Details       TRAFFIC_PORTAL  Traffic
    > Portal
    >     > profile  TP_PROFILE      -       2017-09-05 22:14:37.192758+00
    >     > Profile Details Parameter Details       TRAFFIC_ROUTER  Traffic
    > Router
    >     > profile  TR_PROFILE      -       2017-09-05 22:52:43.543589+00
    >     > Profile Details Parameter Details       TRAFFIC_STATS   Traffic Stats
    >     > profile   TS_PROFILE      -       2017-09-05 22:14:37.193739+00
    >     > Showing 1 to 11 of 11 entries
    >     >
    >     >
    >     > What would be the next step? Create two more VMs, download and build
    > ATS
    >     > on them? Then, where do I start configuring the whole system to be
    > able to
    >     > pass traffic?
    >     >
    >     > Thanks,
    >     > Michael
    >     >
    >     > On 8/31/17, 2:18 PM, "Dave Neuman" <ne...@apache.org> wrote:
    >     >
    >     >     Hey Michael,
    >     >     I have built a "CDN in a box" before using KVM and a physical
    > server
    >     > but I
    >     >     haven't ever tried to build one in AWS.  I think you will need at
    >     > least 3
    >     >     VMs to make this happen.  The first one should be able to run
    > all of
    >     > the TC
    >     >     components (Traffic Ops, Postgres, Traffic Monitor, Traffic
    > Router)
    >     > and you
    >     >     will need at least two caches.  We require at least a two tier
    > CDN
    >     > with at
    >     >     least one EDGE and one MID server.  It might be a little
    > difficult
    >     > getting
    >     >     all of the TC components running on one VM, but I think it can
    > be done.
    >     >
    >     >     Sorry, we don't really have a how-to on doing what you are
    > trying to
    >     > do,
    >     >     but I (and hopefully others) are more than happy to help here.
    >     >
    >     >     Thanks,
    >     >     Dave
    >     >
    >     >     On Thu, Aug 31, 2017 at 2:54 PM, Michael Talyansky <
    >     >     michael.talyansky@ericsson.com> wrote:
    >     >
    >     >     > Hi,
    >     >     >
    >     >     > I am trying to set up development and testing environment on
    > AWS. So
    >     > far,
    >     >     > I have two VMs, one running postgres, and one on which I built
    >     >     > trafficcontrol. I will need to set up at least one caching
    > node, so
    >     > I can
    >     >     > test the whole system.
    >     >     >
    >     >     > Has anyone done something similar before, and if so, is there a
    >     > pointer to
    >     >     > a sample configuration of how to do this with the least amount
    > of
    >     > VMs?
    >     >     >
    >     >     > Thanks in advance!
    >     >     >
    >     >
    >     >
    >     >
    >
    >
    >
    


Re: Initial setup for development

Posted by Mark Torluemke <mt...@apache.org>.
Slack should be fixed now. Also, the TC admin guide has the installation
docs: http://trafficcontrol.apache.org/docs/latest/admin/index.html

On Tue, Sep 5, 2017 at 9:17 PM, Michael Talyansky <
michael.talyansky@ericsson.com> wrote:

> Thanks, Mark,
>
> How do I get onto Slack channel? I submitted a form a few days ago, but
> got no reply. Just re-submitted now. Is this enough to get added?
>
> As far as ATS installation, is it documented as part of the Traffic
> Control, or do I have to go to ATS page for that?
>
> Thanks,
> Michael
>
> On 9/5/17, 7:59 PM, "Mark Torluemke" <mt...@apache.org> wrote:
>
>     Hi Michael,
>
>     If you're trying to optimize over the # of instances, I would lean away
>     from the official production-ready recommendations in the docs, and do
> more
>     of what Dave suggested. Something like this:
>
>     +-----------+-----+
>     | Component | VM  |
>     +-----------+-----+
>     | TO        | VM1 |
>     | TODB      | VM1 |
>     | TV        | VM1 |
>     | TM        | VM1 |
>     | TS        | --  |
>     | Influx    | --  |
>     | TR        | VM2 |
>     | ATS-EDGE  | VM3 |
>     | ATS-MID   | VM4 |
>     | TP        | --  |
>     +-----------+-----+
>
>     The ones with "--" can be added later, if you require that
> functionality.
>     Most of the components should have adequate installation
> documentation, but
>     reply back the list, or find us on Slack (
> traffic-control-cdn.slack.com) if
>     you get stuck.
>
>     Cheers,
>     Mark
>
>
>
>     On Tue, Sep 5, 2017 at 5:07 PM, Michael Talyansky <
>     michael.talyansky@ericsson.com> wrote:
>
>     > Hi Dave,
>     >
>     > Thanks for the offer of help!
>     >
>     > So far, I was able to do the following:
>     >
>     > 1. Create two VMs as recommended on the website, one for postgres
> and one
>     > for TrafficOps
>     > 2. Configure and start Postgres
>     > 3. Download and build Traffic Ops
>     > 4. Verify postgres connectivity and install traffic ops, according
> to this
>     > page: https://trafficcontrol.incubator.apache.org/docs/
>     > latest/admin/traffic_ops/installation.html
>     > 5. Brought up the GUI, downloaded and imported two missing profiles
> for
>     > EDGE_ATS and MID_ATS, so I have 11 profiles listed now:
>     >
>     > Profile Name
>     > Profile Description
>     > Type
>     > Cdn
>     > Last updated
>     > Profile Details Parameter Details       EDGE_ATS_621_CENTOS_721 Edge
> Cache
>     > - Apache Traffic Server v6.2.1-61.1ec1041.el7.centos.x86_64
> ATS_PROFILE
>     >    -       2017-09-05 22:54:57.061084+00
>     > Profile Details Parameter Details       GLOBAL  Global Traffic Ops
>     > profile, DO NOT DELETE       UNK_PROFILE     -       2017-09-05
>     > 22:14:37.180598+00
>     > Profile Details Parameter Details       INFLUXDB        InfluxDb
> profile
>     >       INFLUXDB_PROFILE        -       2017-09-05 22:14:37.194697+00
>     > Profile Details Parameter Details       MID_ATS_532_CENTOS_721  Mid
> Cache
>     > - Apache Traffic Server v5.3.2-762.23d37d0.el7.centos.x86_64
>     > ATS_PROFILE     -       2017-09-05 22:53:35.519531+00
>     > Profile Details Parameter Details       RIAK_ALL        Riak profile
> for
>     > all CDNs       RIAK_PROFILE    -       2017-09-05 22:14:37.195611+00
>     > Profile Details Parameter Details       TRAFFIC_ANALYTICS
>  Traffic
>     > Analytics profile       UNK_PROFILE     -       2017-09-05
>     > 22:14:37.189865+00
>     > Profile Details Parameter Details       TRAFFIC_OPS     Traffic Ops
>     > profile     UNK_PROFILE     -       2017-09-05 22:14:37.190855+00
>     > Profile Details Parameter Details       TRAFFIC_OPS_DB  Traffic Ops
> DB
>     > profile  UNK_PROFILE     -       2017-09-05 22:14:37.191781+00
>     > Profile Details Parameter Details       TRAFFIC_PORTAL  Traffic
> Portal
>     > profile  TP_PROFILE      -       2017-09-05 22:14:37.192758+00
>     > Profile Details Parameter Details       TRAFFIC_ROUTER  Traffic
> Router
>     > profile  TR_PROFILE      -       2017-09-05 22:52:43.543589+00
>     > Profile Details Parameter Details       TRAFFIC_STATS   Traffic Stats
>     > profile   TS_PROFILE      -       2017-09-05 22:14:37.193739+00
>     > Showing 1 to 11 of 11 entries
>     >
>     >
>     > What would be the next step? Create two more VMs, download and build
> ATS
>     > on them? Then, where do I start configuring the whole system to be
> able to
>     > pass traffic?
>     >
>     > Thanks,
>     > Michael
>     >
>     > On 8/31/17, 2:18 PM, "Dave Neuman" <ne...@apache.org> wrote:
>     >
>     >     Hey Michael,
>     >     I have built a "CDN in a box" before using KVM and a physical
> server
>     > but I
>     >     haven't ever tried to build one in AWS.  I think you will need at
>     > least 3
>     >     VMs to make this happen.  The first one should be able to run
> all of
>     > the TC
>     >     components (Traffic Ops, Postgres, Traffic Monitor, Traffic
> Router)
>     > and you
>     >     will need at least two caches.  We require at least a two tier
> CDN
>     > with at
>     >     least one EDGE and one MID server.  It might be a little
> difficult
>     > getting
>     >     all of the TC components running on one VM, but I think it can
> be done.
>     >
>     >     Sorry, we don't really have a how-to on doing what you are
> trying to
>     > do,
>     >     but I (and hopefully others) are more than happy to help here.
>     >
>     >     Thanks,
>     >     Dave
>     >
>     >     On Thu, Aug 31, 2017 at 2:54 PM, Michael Talyansky <
>     >     michael.talyansky@ericsson.com> wrote:
>     >
>     >     > Hi,
>     >     >
>     >     > I am trying to set up development and testing environment on
> AWS. So
>     > far,
>     >     > I have two VMs, one running postgres, and one on which I built
>     >     > trafficcontrol. I will need to set up at least one caching
> node, so
>     > I can
>     >     > test the whole system.
>     >     >
>     >     > Has anyone done something similar before, and if so, is there a
>     > pointer to
>     >     > a sample configuration of how to do this with the least amount
> of
>     > VMs?
>     >     >
>     >     > Thanks in advance!
>     >     >
>     >
>     >
>     >
>
>
>

Re: Initial setup for development

Posted by Michael Talyansky <mi...@ericsson.com>.
Thanks, Mark,

How do I get onto Slack channel? I submitted a form a few days ago, but got no reply. Just re-submitted now. Is this enough to get added?

As far as ATS installation, is it documented as part of the Traffic Control, or do I have to go to ATS page for that?

Thanks,
Michael

On 9/5/17, 7:59 PM, "Mark Torluemke" <mt...@apache.org> wrote:

    Hi Michael,
    
    If you're trying to optimize over the # of instances, I would lean away
    from the official production-ready recommendations in the docs, and do more
    of what Dave suggested. Something like this:
    
    +-----------+-----+
    | Component | VM  |
    +-----------+-----+
    | TO        | VM1 |
    | TODB      | VM1 |
    | TV        | VM1 |
    | TM        | VM1 |
    | TS        | --  |
    | Influx    | --  |
    | TR        | VM2 |
    | ATS-EDGE  | VM3 |
    | ATS-MID   | VM4 |
    | TP        | --  |
    +-----------+-----+
    
    The ones with "--" can be added later, if you require that functionality.
    Most of the components should have adequate installation documentation, but
    reply back the list, or find us on Slack (traffic-control-cdn.slack.com) if
    you get stuck.
    
    Cheers,
    Mark
    
    
    
    On Tue, Sep 5, 2017 at 5:07 PM, Michael Talyansky <
    michael.talyansky@ericsson.com> wrote:
    
    > Hi Dave,
    >
    > Thanks for the offer of help!
    >
    > So far, I was able to do the following:
    >
    > 1. Create two VMs as recommended on the website, one for postgres and one
    > for TrafficOps
    > 2. Configure and start Postgres
    > 3. Download and build Traffic Ops
    > 4. Verify postgres connectivity and install traffic ops, according to this
    > page: https://trafficcontrol.incubator.apache.org/docs/
    > latest/admin/traffic_ops/installation.html
    > 5. Brought up the GUI, downloaded and imported two missing profiles for
    > EDGE_ATS and MID_ATS, so I have 11 profiles listed now:
    >
    > Profile Name
    > Profile Description
    > Type
    > Cdn
    > Last updated
    > Profile Details Parameter Details       EDGE_ATS_621_CENTOS_721 Edge Cache
    > - Apache Traffic Server v6.2.1-61.1ec1041.el7.centos.x86_64  ATS_PROFILE
    >    -       2017-09-05 22:54:57.061084+00
    > Profile Details Parameter Details       GLOBAL  Global Traffic Ops
    > profile, DO NOT DELETE       UNK_PROFILE     -       2017-09-05
    > 22:14:37.180598+00
    > Profile Details Parameter Details       INFLUXDB        InfluxDb profile
    >       INFLUXDB_PROFILE        -       2017-09-05 22:14:37.194697+00
    > Profile Details Parameter Details       MID_ATS_532_CENTOS_721  Mid Cache
    > - Apache Traffic Server v5.3.2-762.23d37d0.el7.centos.x86_64
    > ATS_PROFILE     -       2017-09-05 22:53:35.519531+00
    > Profile Details Parameter Details       RIAK_ALL        Riak profile for
    > all CDNs       RIAK_PROFILE    -       2017-09-05 22:14:37.195611+00
    > Profile Details Parameter Details       TRAFFIC_ANALYTICS       Traffic
    > Analytics profile       UNK_PROFILE     -       2017-09-05
    > 22:14:37.189865+00
    > Profile Details Parameter Details       TRAFFIC_OPS     Traffic Ops
    > profile     UNK_PROFILE     -       2017-09-05 22:14:37.190855+00
    > Profile Details Parameter Details       TRAFFIC_OPS_DB  Traffic Ops DB
    > profile  UNK_PROFILE     -       2017-09-05 22:14:37.191781+00
    > Profile Details Parameter Details       TRAFFIC_PORTAL  Traffic Portal
    > profile  TP_PROFILE      -       2017-09-05 22:14:37.192758+00
    > Profile Details Parameter Details       TRAFFIC_ROUTER  Traffic Router
    > profile  TR_PROFILE      -       2017-09-05 22:52:43.543589+00
    > Profile Details Parameter Details       TRAFFIC_STATS   Traffic Stats
    > profile   TS_PROFILE      -       2017-09-05 22:14:37.193739+00
    > Showing 1 to 11 of 11 entries
    >
    >
    > What would be the next step? Create two more VMs, download and build ATS
    > on them? Then, where do I start configuring the whole system to be able to
    > pass traffic?
    >
    > Thanks,
    > Michael
    >
    > On 8/31/17, 2:18 PM, "Dave Neuman" <ne...@apache.org> wrote:
    >
    >     Hey Michael,
    >     I have built a "CDN in a box" before using KVM and a physical server
    > but I
    >     haven't ever tried to build one in AWS.  I think you will need at
    > least 3
    >     VMs to make this happen.  The first one should be able to run all of
    > the TC
    >     components (Traffic Ops, Postgres, Traffic Monitor, Traffic Router)
    > and you
    >     will need at least two caches.  We require at least a two tier CDN
    > with at
    >     least one EDGE and one MID server.  It might be a little difficult
    > getting
    >     all of the TC components running on one VM, but I think it can be done.
    >
    >     Sorry, we don't really have a how-to on doing what you are trying to
    > do,
    >     but I (and hopefully others) are more than happy to help here.
    >
    >     Thanks,
    >     Dave
    >
    >     On Thu, Aug 31, 2017 at 2:54 PM, Michael Talyansky <
    >     michael.talyansky@ericsson.com> wrote:
    >
    >     > Hi,
    >     >
    >     > I am trying to set up development and testing environment on AWS. So
    > far,
    >     > I have two VMs, one running postgres, and one on which I built
    >     > trafficcontrol. I will need to set up at least one caching node, so
    > I can
    >     > test the whole system.
    >     >
    >     > Has anyone done something similar before, and if so, is there a
    > pointer to
    >     > a sample configuration of how to do this with the least amount of
    > VMs?
    >     >
    >     > Thanks in advance!
    >     >
    >
    >
    >
    


Re: Initial setup for development

Posted by Mark Torluemke <mt...@apache.org>.
Hi Michael,

If you're trying to optimize over the # of instances, I would lean away
from the official production-ready recommendations in the docs, and do more
of what Dave suggested. Something like this:

+-----------+-----+
| Component | VM  |
+-----------+-----+
| TO        | VM1 |
| TODB      | VM1 |
| TV        | VM1 |
| TM        | VM1 |
| TS        | --  |
| Influx    | --  |
| TR        | VM2 |
| ATS-EDGE  | VM3 |
| ATS-MID   | VM4 |
| TP        | --  |
+-----------+-----+

The ones with "--" can be added later, if you require that functionality.
Most of the components should have adequate installation documentation, but
reply back the list, or find us on Slack (traffic-control-cdn.slack.com) if
you get stuck.

Cheers,
Mark



On Tue, Sep 5, 2017 at 5:07 PM, Michael Talyansky <
michael.talyansky@ericsson.com> wrote:

> Hi Dave,
>
> Thanks for the offer of help!
>
> So far, I was able to do the following:
>
> 1. Create two VMs as recommended on the website, one for postgres and one
> for TrafficOps
> 2. Configure and start Postgres
> 3. Download and build Traffic Ops
> 4. Verify postgres connectivity and install traffic ops, according to this
> page: https://trafficcontrol.incubator.apache.org/docs/
> latest/admin/traffic_ops/installation.html
> 5. Brought up the GUI, downloaded and imported two missing profiles for
> EDGE_ATS and MID_ATS, so I have 11 profiles listed now:
>
> Profile Name
> Profile Description
> Type
> Cdn
> Last updated
> Profile Details Parameter Details       EDGE_ATS_621_CENTOS_721 Edge Cache
> - Apache Traffic Server v6.2.1-61.1ec1041.el7.centos.x86_64  ATS_PROFILE
>    -       2017-09-05 22:54:57.061084+00
> Profile Details Parameter Details       GLOBAL  Global Traffic Ops
> profile, DO NOT DELETE       UNK_PROFILE     -       2017-09-05
> 22:14:37.180598+00
> Profile Details Parameter Details       INFLUXDB        InfluxDb profile
>       INFLUXDB_PROFILE        -       2017-09-05 22:14:37.194697+00
> Profile Details Parameter Details       MID_ATS_532_CENTOS_721  Mid Cache
> - Apache Traffic Server v5.3.2-762.23d37d0.el7.centos.x86_64
> ATS_PROFILE     -       2017-09-05 22:53:35.519531+00
> Profile Details Parameter Details       RIAK_ALL        Riak profile for
> all CDNs       RIAK_PROFILE    -       2017-09-05 22:14:37.195611+00
> Profile Details Parameter Details       TRAFFIC_ANALYTICS       Traffic
> Analytics profile       UNK_PROFILE     -       2017-09-05
> 22:14:37.189865+00
> Profile Details Parameter Details       TRAFFIC_OPS     Traffic Ops
> profile     UNK_PROFILE     -       2017-09-05 22:14:37.190855+00
> Profile Details Parameter Details       TRAFFIC_OPS_DB  Traffic Ops DB
> profile  UNK_PROFILE     -       2017-09-05 22:14:37.191781+00
> Profile Details Parameter Details       TRAFFIC_PORTAL  Traffic Portal
> profile  TP_PROFILE      -       2017-09-05 22:14:37.192758+00
> Profile Details Parameter Details       TRAFFIC_ROUTER  Traffic Router
> profile  TR_PROFILE      -       2017-09-05 22:52:43.543589+00
> Profile Details Parameter Details       TRAFFIC_STATS   Traffic Stats
> profile   TS_PROFILE      -       2017-09-05 22:14:37.193739+00
> Showing 1 to 11 of 11 entries
>
>
> What would be the next step? Create two more VMs, download and build ATS
> on them? Then, where do I start configuring the whole system to be able to
> pass traffic?
>
> Thanks,
> Michael
>
> On 8/31/17, 2:18 PM, "Dave Neuman" <ne...@apache.org> wrote:
>
>     Hey Michael,
>     I have built a "CDN in a box" before using KVM and a physical server
> but I
>     haven't ever tried to build one in AWS.  I think you will need at
> least 3
>     VMs to make this happen.  The first one should be able to run all of
> the TC
>     components (Traffic Ops, Postgres, Traffic Monitor, Traffic Router)
> and you
>     will need at least two caches.  We require at least a two tier CDN
> with at
>     least one EDGE and one MID server.  It might be a little difficult
> getting
>     all of the TC components running on one VM, but I think it can be done.
>
>     Sorry, we don't really have a how-to on doing what you are trying to
> do,
>     but I (and hopefully others) are more than happy to help here.
>
>     Thanks,
>     Dave
>
>     On Thu, Aug 31, 2017 at 2:54 PM, Michael Talyansky <
>     michael.talyansky@ericsson.com> wrote:
>
>     > Hi,
>     >
>     > I am trying to set up development and testing environment on AWS. So
> far,
>     > I have two VMs, one running postgres, and one on which I built
>     > trafficcontrol. I will need to set up at least one caching node, so
> I can
>     > test the whole system.
>     >
>     > Has anyone done something similar before, and if so, is there a
> pointer to
>     > a sample configuration of how to do this with the least amount of
> VMs?
>     >
>     > Thanks in advance!
>     >
>
>
>