Sorry, I have been out the last few days and I was holding off on my vote
on purpose.  Last week I installed Traffic Ops and I noticed that all of
the default data that I expected to be there was not there.  For example,
default EDGE and MID profiles were not created, same for the default
parameters for those profiles.  I asked if this was expected in slack, but
I didn't see a repose (or I was already out of office when someone did
respond).  I think it's important that a clean install properly populates
enough default data that someone can understand how to use our system.  I
was trying to avoid a -1 without first confirming it was a real issue.

Thanks,
Dave

On Mon, Jun 12, 2017 at 7:04 AM, Eric Friedrich (efriedri) <
[email protected]> wrote:

> The time period for the vote is up, but I’m looking for a few more votes.
>
> So far we have 2 +1s, but I don’t think anyone has actually installed the
> RC yet.
>
> Thanks,
> Eric
> > On Jun 8, 2017, at 12:40 PM, Dan Kirkwood <[email protected]> wrote:
> >
> > you're right -- it shouldn't..   thanks!
> >
> > On Thu, Jun 8, 2017 at 10:39 AM, Hank Beatty <[email protected]> wrote:
> >> I just realized it is our cdn.conf that doesn't have the secrets in it
> not
> >> the default. Still don't think it should error. I'll fix it and submit
> the
> >> PR.
> >>
> >> On 06/08/2017 11:30 AM, Dan Kirkwood wrote:
> >>>
> >>> not that I'm aware of...  please do file an issue for it,  though and
> >>> attach that to the PR.
> >>>
> >>> thanks!  Dan
> >>>
> >>> On Thu, Jun 8, 2017 at 9:18 AM, Hank Beatty <[email protected]>
> wrote:
> >>>>
> >>>> postinstall might still be broken:
> >>>>
> >>>> Password for database server admin:
> >>>> Re-Enter Password for database server admin:
> >>>> Download Maxmind Database? [yes]:
> >>>> Download Maxmind Database?: yes
> >>>> ===========/opt/traffic_ops/app/conf/cdn.conf===========
> >>>> Generate a new secret? [yes]:
> >>>> Generate a new secret?: yes
> >>>> Number of secrets to keep? [10]:
> >>>> Number of secrets to keep?: 10
> >>>> Can't use an undefined value as an ARRAY reference at
> >>>> /opt/traffic_ops/install/bin/_postinstall line 211, <STDIN> line 13.
> >>>>
> >>>> And I've already started looking into it...
> >>>>
> >>>> It is trying to load the secrets from the cdn.conf file. The initial
> >>>> cdn.conf file doesn't have any secrets. I can fix the _postinstall to
> >>>> correct this and do a PR.
> >>>>
> >>>> Unless someone else has already fixed it or it needs to be done a
> >>>> different
> >>>> way.
> >>>>
> >>>> Thanks,
> >>>> Hank
> >>>>
> >>>> On 06/05/2017 02:16 PM, Eric Friedrich (efriedri) wrote:
> >>>>>
> >>>>>
> >>>>> Hello All,
> >>>>>
> >>>>> I've prepared the next candidate release for incubator-trafficcontrol
> >>>>> v2.0.0 (RC4)
> >>>>>
> >>>>> Changes since 1.8.0:
> >>>>>
> >>>>>
> >>>>> https://github.com/apache/incubator-trafficcontrol/
> compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC4<https://
> github.com/apache/incubator-trafficcontrol/compare/
> RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC3>
> >>>>>
> >>>>> This corresponds to git:
> >>>>> Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30
> >>>>> Tag: RELEASE-2.0.0-RC4
> >>>>>
> >>>>> Which can be verified with the following:    git tag -v
> >>>>> RELEASE-2.0.0-RC4
> >>>>>
> >>>>> My code signing key is available here:
> >>>>> http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5
> >>>>>
> >>>>> and here:
> >>>>> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
> >>>>>
> >>>>> Make sure you refresh from a key server to get all relevant
> signatures.
> >>>>>
> >>>>> The source .tar.gz file, pgp signature (.asc signed with my key from
> >>>>> above), and md5 and sha512 checksums are provided here:
> >>>>>
> >>>>> https://dist.apache.org/repos/dist/dev/incubator/
> trafficcontrol/2.0.0/RC4
> >>>>>
> >>>>>
> >>>>> The vote will remain open until Thursday, June 8, 2017.
> >>>>>
> >>>>> This RC fixes some packaging issues in RC2 and RC3, there are no
> other
> >>>>> changes. The git tag hash is the same, but due to changes in the
> tarball
> >>>>> the
> >>>>> release signatures HAVE changes.
> >>>>>
> >>>>> Thanks,
> >>>>> Eric Friedrich
> >>>>>
> >>>>
> >>
>
>

Reply via email to