Re: [VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Maxime Beauchemin]

@Alan, looks like I messed up the signature somehow. I got tangled into
adding a new entry (moving from my gmail to my apache.org address),
deleting the old one and my svn kungfu is beyond rusty...

Oh I think I just forgot to run "svn commit" (maybe i ran "svn update"
instead?), so you should just have to import that new KEYS file and it
should work.

Sorry about the confusion. All of this is pretty error-prone, especially
the [few] first time[s] around.

Max

On Mon, May 20, 2019 at 11:29 AM Abhishek Sharma 
wrote:

> +1 binding.
>
> Newly built docker image
> <
> https://cloud.docker.com/u/abhioncbr/repository/docker/abhioncbr/docker-superset
> >
> working fine.
>
> Thanks
> Abhishek
>
> On Mon, May 20, 2019 at 2:03 PM Alan Gates  wrote:
>
> > Max, when I check the signature (gpg --verify ) it tells me:
> > gpg: Signature made Sat May 18 15:36:55 2019 PDT
> > gpg:using RSA key
> 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
> > gpg: Can't check signature: No public key
> >
> > I imported the KEYS file referenced in your message, but it doesn't
> appear
> > to contain that key.  I think you need to either generate a new signature
> > with the key in the file and upload that .asc file to the dist site (no
> > need to rerole the release itself) or place the key you used into the
> KEYS
> > file.
> >
> > Alan.
> >
> > On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > Dear all,
> > >
> > > The source release 0.33.0 RC1 for Apache Superset is baked and
> available
> > > at:
> > > https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> > > keys are available
> > > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > >
> > > We're now attempting to use 0.33 as the base for the first release as
> > > opposed to 0.32 in previous attempts. Many license-related issues had
> > been
> > > solved by the process shipping visualizations as plugins, and that
> > > migration wasn't completed on 0.32. This is the third ASF release
> > candidate
> > > of Superset *We're still ironing out our release process, so please
> bear
> > > with us and help if you can*.
> > >
> > > As I went along, I documented the process in [yet-to-be-merged]
> > > RELEASING/README.md in the repo, latest edits here
> > > https://github.com/apache/incubator-superset/pull/7539 . As part of
> > > `RELEASING/`, we ship docker files to help package and test releases.
> > >
> > > For context the `0.33` release branch was cut at SHA 51068f007, that
> was
> > > merged on master on Apr 17th. From that common ancestor, the following
> > list
> > > of commit was added as cherry-picks. The SHAs in the list bellow
> > reference
> > > the cherries on the release branch, PR number are available to get more
> > > details.
> > >
> > > 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> > > b7ffdb8b Improve instructions
> > > 4bbd68c6 Change babytux to open image in birth dashboard
> > > eaa679e8 remove unused LICENSE entries
> > > 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> > > 5ae2836b Address COPYRIGHT + LICENSE issues
> > > ea807f20 [WiP] Improvements related to ASF release process
> > > c57ef5dc 0.31.0rc1.dev1
> > > 51068f00 Adding permission for can_only_access_owned_queries (#7234)
> > >
> >
>

Re: Superset production setup

[John Bodley]

Hi Matthew,

In answer to your questions (from Airbnb's perspective):

   1. Regarding a production environment it's probably highly dependent on
   your use case. At a minimum I would suggest having at least 3 web-servers
   (we use Gunicorn ) and 3 Celery workers for
   redundancy. We use Datadog for monitoring/alerting which has helped us
   track load and scale accordingly. We use Kubernetes for deployment which
   includes some elasticity, though currently we're running 3 web-servers and
   5+ Celery workers. The later may be overkill though we're trying to debug
   an ongoing QueuePool issue.
   2. We use AWS to house Redis, Superset, Celery, etc. which all run from
   the same region
   

   .
   3. Our servers run on 4 cores with 10 GB of memory. Note we haven't
   optimized this configuration.
   4. We have low thousands of weekly active users for Superset and SQL
   Lab.

-John




On Mon, May 20, 2019 at 12:24 AM Matthew Mutee  wrote:

> Hi dev,
>
> We have been testing superset for the last couple of months and now want to
> set it up in production. Could you please share what sort of resourcing
> considerations you have made for  your superset installation.
>
> I am interested in:
>
>1. Number of servers used for load balancing.
>2. Placement of  applications; redis, superset, celelery, nginx etc.
>3. Actual resources in the servers; memory, cores etc
>4. The average users accessing superset per day.
>
> Thanks :-)
>
> Regards,
> Matthew M.
>

Re: [VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Abhishek Sharma]

+1 binding.

Newly built docker image

working fine.

Thanks
Abhishek

On Mon, May 20, 2019 at 2:03 PM Alan Gates  wrote:

> Max, when I check the signature (gpg --verify ) it tells me:
> gpg: Signature made Sat May 18 15:36:55 2019 PDT
> gpg:using RSA key 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
> gpg: Can't check signature: No public key
>
> I imported the KEYS file referenced in your message, but it doesn't appear
> to contain that key.  I think you need to either generate a new signature
> with the key in the file and upload that .asc file to the dist site (no
> need to rerole the release itself) or place the key you used into the KEYS
> file.
>
> Alan.
>
> On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Dear all,
> >
> > The source release 0.33.0 RC1 for Apache Superset is baked and available
> > at:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> > keys are available
> > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> >
> > We're now attempting to use 0.33 as the base for the first release as
> > opposed to 0.32 in previous attempts. Many license-related issues had
> been
> > solved by the process shipping visualizations as plugins, and that
> > migration wasn't completed on 0.32. This is the third ASF release
> candidate
> > of Superset *We're still ironing out our release process, so please bear
> > with us and help if you can*.
> >
> > As I went along, I documented the process in [yet-to-be-merged]
> > RELEASING/README.md in the repo, latest edits here
> > https://github.com/apache/incubator-superset/pull/7539 . As part of
> > `RELEASING/`, we ship docker files to help package and test releases.
> >
> > For context the `0.33` release branch was cut at SHA 51068f007, that was
> > merged on master on Apr 17th. From that common ancestor, the following
> list
> > of commit was added as cherry-picks. The SHAs in the list bellow
> reference
> > the cherries on the release branch, PR number are available to get more
> > details.
> >
> > 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> > b7ffdb8b Improve instructions
> > 4bbd68c6 Change babytux to open image in birth dashboard
> > eaa679e8 remove unused LICENSE entries
> > 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> > 5ae2836b Address COPYRIGHT + LICENSE issues
> > ea807f20 [WiP] Improvements related to ASF release process
> > c57ef5dc 0.31.0rc1.dev1
> > 51068f00 Adding permission for can_only_access_owned_queries (#7234)
> >
>

Re: [VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Alan Gates]

Max, when I check the signature (gpg --verify ) it tells me:
gpg: Signature made Sat May 18 15:36:55 2019 PDT
gpg:using RSA key 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
gpg: Can't check signature: No public key

I imported the KEYS file referenced in your message, but it doesn't appear
to contain that key.  I think you need to either generate a new signature
with the key in the file and upload that .asc file to the dist site (no
need to rerole the release itself) or place the key you used into the KEYS
file.

Alan.

On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.33.0 RC1 for Apache Superset is baked and available
> at:
> https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> keys are available
> at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> We're now attempting to use 0.33 as the base for the first release as
> opposed to 0.32 in previous attempts. Many license-related issues had been
> solved by the process shipping visualizations as plugins, and that
> migration wasn't completed on 0.32. This is the third ASF release candidate
> of Superset *We're still ironing out our release process, so please bear
> with us and help if you can*.
>
> As I went along, I documented the process in [yet-to-be-merged]
> RELEASING/README.md in the repo, latest edits here
> https://github.com/apache/incubator-superset/pull/7539 . As part of
> `RELEASING/`, we ship docker files to help package and test releases.
>
> For context the `0.33` release branch was cut at SHA 51068f007, that was
> merged on master on Apr 17th. From that common ancestor, the following list
> of commit was added as cherry-picks. The SHAs in the list bellow reference
> the cherries on the release branch, PR number are available to get more
> details.
>
> 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> b7ffdb8b Improve instructions
> 4bbd68c6 Change babytux to open image in birth dashboard
> eaa679e8 remove unused LICENSE entries
> 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> 5ae2836b Address COPYRIGHT + LICENSE issues
> ea807f20 [WiP] Improvements related to ASF release process
> c57ef5dc 0.31.0rc1.dev1
> 51068f00 Adding permission for can_only_access_owned_queries (#7234)
>

Re: [VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Ville Brofeldt]

+1 binding

Built locally from source and tested without problems. Third time's
the charm!

Ville


On Sun, May 19, 2019 at 2:01 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.33.0 RC1 for Apache Superset is baked and available
> at:
> https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> keys are available
> at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> We're now attempting to use 0.33 as the base for the first release as
> opposed to 0.32 in previous attempts. Many license-related issues had been
> solved by the process shipping visualizations as plugins, and that
> migration wasn't completed on 0.32. This is the third ASF release candidate
> of Superset *We're still ironing out our release process, so please bear
> with us and help if you can*.
>
> As I went along, I documented the process in [yet-to-be-merged]
> RELEASING/README.md in the repo, latest edits here
> https://github.com/apache/incubator-superset/pull/7539 . As part of
> `RELEASING/`, we ship docker files to help package and test releases.
>
> For context the `0.33` release branch was cut at SHA 51068f007, that was
> merged on master on Apr 17th. From that common ancestor, the following list
> of commit was added as cherry-picks. The SHAs in the list bellow reference
> the cherries on the release branch, PR number are available to get more
> details.
>
> 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> b7ffdb8b Improve instructions
> 4bbd68c6 Change babytux to open image in birth dashboard
> eaa679e8 remove unused LICENSE entries
> 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> 5ae2836b Address COPYRIGHT + LICENSE issues
> ea807f20 [WiP] Improvements related to ASF release process
> c57ef5dc 0.31.0rc1.dev1
> 51068f00 Adding permission for can_only_access_owned_queries (#7234)
>

Superset production setup

[Matthew Mutee]

Hi dev,

We have been testing superset for the last couple of months and now want to
set it up in production. Could you please share what sort of resourcing
considerations you have made for  your superset installation.

I am interested in:

   1. Number of servers used for load balancing.
   2. Placement of  applications; redis, superset, celelery, nginx etc.
   3. Actual resources in the servers; memory, cores etc
   4. The average users accessing superset per day.

Thanks :-)

Regards,
Matthew M.